Re: Making a (quick) commit to another branch

2013-04-27 Thread Johannes Schneider
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27.04.2013 16:21, Javier Domingo wrote: > I would first recommend you, instead of cherry-picking the commit, > you did this: -- stash -- go to the master branch -- fix the line > -- commit the fix -- got to the feature branch -- unstash Yeah, of c

Re: Making a (quick) commit to another branch

2013-04-27 Thread Patrik Gornicz
I've also encountered this desire to quickly fix something in another branch. My need is more driven by the fact that it's a large project and stashing changes / switching branches frequently results in 2-6 minute build times afterward. Thus the commit to another branch suggestion would be qu

Re: Making a (quick) commit to another branch

2013-04-27 Thread Javier Domingo
2013/4/27 Johannes Schneider : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi guys, > > I love git. And I use it every day. But there is one minor thing, that > bugs me a little bit: > I am implementing something on a feature branch. Now I detect a minor > typo/bug/whatever that just need

Making a (quick) commit to another branch

2013-04-27 Thread Johannes Schneider
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys, I love git. And I use it every day. But there is one minor thing, that bugs me a little bit: I am implementing something on a feature branch. Now I detect a minor typo/bug/whatever that just needs a one line commit. But of course I don't wan