public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: linux-ext4@vger.kernel.org
Subject: Ext4 Patch Queue using stgit.
Date: Fri, 18 May 2007 18:12:23 +0530	[thread overview]
Message-ID: <464D9F2F.3030904@linux.vnet.ibm.com> (raw)

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

             reply	other threads:[~2007-05-18 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 12:42 Aneesh Kumar K.V [this message]
2007-05-18 13:23 ` Ext4 Patch Queue using stgit Dave Kleikamp
2007-05-18 14:25   ` Aneesh Kumar K.V
2007-05-18 16:06 ` Theodore Tso
2007-05-18 17:09   ` Aneesh Kumar K.V

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=464D9F2F.3030904@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox