On Wed, Nov 21, 2007 at 09:17:59PM +0800, Ping Yin wrote: > On Nov 21, 2007 9:11 PM, Ping Yin <pkufranky@xxxxxxxxx> wrote: > > I have scanned the manual and found a 'Linux subsystem maintainer' > > example. However, that's a little brief and i wonder a more real > > example. I think an example of how to cook git as a maintainer is > > better. > > > > Junio , could you please share the whole process of cooking among pu, > > next and master? Or, can i find this in the mail list archive? > > > > For example: > > In which branch the test is performed? > > How to rewind pu? > > How to merge a subset of changes from pu to next, and from next to master? > > > > One more question: > I see so many merges in pu branch, but where these merges go when a > feature is moved to the master branch? There is a discussion of some of these issues in the mail thread beginning here: http://kerneltrap.org/mailarchive/git/2007/10/23/350943 The git setup is actually pretty complex, and all of the details of how to maintain the pu and next branches are pretty complicated --- and if you don't have a large development community, it may not be worth the overhead, and it may scare people off as being too complicated. There are multiple ways to maintain a project in git, and it's usually better to start simple --- with a development and maintenance branch. If you need more, you can add more later, but I wouldn't recommend starting off with a very complex system right off the bat. - Ted - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
