Re: Linux 2.6.12-rc3

[Pavel Machek <pavel@suse.cz>]

Hi!

> > > > 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"?
> > 
> > Yeah, getting Andrew into the picture is a bit different.
> 
> Andrew has some work to do before he can regain momentum:
> 
> - Which subsystem maintainers will have public git trees?

I'd like to use git. It sucks for actuall development, but seems to be
very usefull for taking nice and clean patches from people...

> - Which maintainers will continue to use bk?
> 
> - Can Andrew legally use the bk client?

I guess you need to Cc Larry on this one....
								Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/