Re: simple (and probably trivial) git question about cumulative patches
2007-11-01 01:38:24 GMT
On 10/31/2007 09:57 AM, Ramagudi Naziir wrote: > On 10/31/07, Rene Herman <rene.herman <at> keyaccess.nl> wrote: >> Quilt is tool to manage a stack of patches. You push and pop patches >> and there's always one on top. I've used it a while, but did not find >> it to be very handy for managing trees you do actual development in. >> Working on anything but the patch on top of the stack is somewhere >> between impossible and ill adviced with it, and I frequently found >> myself realizing I needed to work on earlier patches a bit more. You >> then have to pop everything that's on top, work, commit, push all the >> others again (and suffering maybe massive recompiles due to touching >> many files...) and so on. > > This is the same problem I have with git (I have never tried quilt). How > can you work an an earlier patch in git ? I also do exactly what you said > - I pop everything on top... work.. commit.. push back all others... do > you have a way to do this otherwise using git ? Well, firstly, I use seperate branches for most anything. My master branch tracks linus' tree but I'm only on that branch when I want to upgrade to a new upstream which I don't do daily or anything. I branch off for anything conceptually seperate and have a "local" branch that pulls in all the other branches that contains work I want to compile, and which generates the kernel I run. I usually branch of at a full release: <at the master branch> git branch foo v2.6.23(Continue reading)
RSS Feed