Messages in this thread | | | Date | Mon, 30 Nov 2009 08:57:13 +1100 | From | Stephen Rothwell <> | Subject | Re: linux-kbuild.git |
| |
Hi Michal,
On Fri, 27 Nov 2009 10:42:37 +0100 Michal Marek <mmarek@suse.cz> wrote: > > > Do you intend to run the equivalent of > > the kbuild-current tree (bug fixes for the current release while they are > > waiting to go to Linus)? I have removed the kbuild-current tree for now > > since the only commit in it is in the new kbuild tree. > > I plan to maintain such a branch, but I thought I would base the > for-next branch on top of it, so that you get everything in one pack. Or > would you still prefer to have two kbuild branches in linux-next, so > that you can remove the for-next branch if necessary and keep the > for-current branch? Just tell me what fits you best.
Running a for-current branch allows you to queue up urgent fixes without disrupting your for-next branch. I will merge such a branch early on (actually before I do my first build) so that I don't have to worry about problems that are already have fixes pending for to be merged by Linus in his current tree. Also, as you say, if I have problems with your for-next branch, it does not affect the more urgent patches.
-- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ [unhandled content-type:application/pgp-signature] | |