Re: Linux 2.6.12-rc3

[Pavel Machek <pavel@ucw.cz>]

Hi!

> > > A word of warning: in many ways it's easier to work with patches. In
> > > particular, if you want to have me merge from your tree, I require a
> > > certain amount of cleanliness in the trees I'm pulling from. All of the
> > > people who used to use BK to sync are already used to that, but for people
> > > who didn't historically use BK this is going to be a learning experience.
> > > 
> > 
> > Is there a summary available of the major issues here so that we who are
> > new to this can get up to speed fairly quickly?
> 
> The main issue is if you want to use git for development and accepting
> patches from others, you need to be used to not using that git tree to
> send patches to Linus.  To send patches to him, do something like the
> following:
> 	- export the patches from your git tree
> 	- pick and choose what you want to send off, cleaning up the
> 	  changelog comments and merging patches that need to be.
> 	- clone the latest copy of Linus's tree.
> 	- apply the patches to that tree.
> 	- make the tree public
> 	- generate an email with the diffs and send that off to lkml and
> 	  Linus.
> 
> Because of all of this, I've found that it is easier to use quilt for
> day-to-day development and acceptance of patches.  Then use git to build
> up trees for Linus to pull from.
> 
> But you might find your workflow is different :)

How does Andrew fit into this picture, btw? I thought all patches ought
to go through him... Is Andrew willing to pull from git trees? Or is
it "create one version for akpm, and when he ACKs it, create another
for Linus"?

								Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.