On Fri, 2007-05-18 at 18:12 +0530, Aneesh Kumar K.V wrote: > Hi All, > > I was looking at ext4 patch queue and was wondering why we are putting > .patch under git. If we are looking for a quilt like functionality, one > can achieve the same using stgit. I was using stgit to maintain a set of > patches before. So if you look at > > http://git.openssi.org/~kvaneesh/gitweb.cgi?p=ci-to-linus.git;a=summary > > you will see the patches i was working on with linus tree as from-linus. > Now to find out what changes were made to these patches during the > development one can look at the tracking branch. In the above case the > latest tracking branch was 2.6.20-rc1-ci-to-linus > > http://git.openssi.org/~kvaneesh/gitweb.cgi?h=2.6.20-rc1-ci-to-linus;p=ci-to-linus.git;a=shortlog > > Other tracking branches at different development stages can be found at > http://git.openssi.org/~kvaneesh/gitweb.cgi?p=ci-to-linus.git;a=heads > > > This make looking at the diff much easier. diff of .patch does seems to > be useful. Does _not_ seem to be useful? I agree that I find the current setup a little awkward. The git tree isn't something we can point Andrew or Linus to. It has to be extracted to another place for that. We really should have some of these patches in mainline by now, and that's not getting done. I haven't looked at stgit, so I don't have an opinion on using it as an alternative, but I'm open to the idea. > Only problem i can think of is how multiple people will push to the same > repo. If we continue to host on repo.or.cz, Ted can allow anyone he wants to push to the tree. Thanks, Shaggy -- David Kleikamp IBM Linux Technology Center - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
