linux-ext4 - Ext4 Patch Queue using stgit.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 May 2007 18:12:23 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	linux-ext4@...r.kernel.org
Subject: Ext4 Patch Queue using stgit.

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.

Only problem i can think of is how multiple people will push to the same 
repo.

-aneesh

-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html