All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 Patch Queue using stgit.
Date: Fri, 18 May 2007 22:39:49 +0530	[thread overview]
Message-ID: <464DDDDD.7080308@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070518160626.GA19911@thunk.org>



Theodore Tso wrote:
> On Fri, May 18, 2007 at 06:12:23PM +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. 
> 
> The problem with stgit is that you lose the history of the patches.
> This is why the stable kernel queue is also kept as a git repository
> of patches.
> 
> 

What i used to do with

http://git.openssi.org/~kvaneesh/gitweb.cgi?p=ci-to-linus.git;a=summary

is after doing stg refresh, push all the patches and then commit the 
diff between the head of the master (which is managed by stgit ) and one 
of the tracking branches to the tracking branch. That way the history of 
the patches can be tracked in the tracking branches. In my previous mail 
i have marked the below urls as eg:

http://git.openssi.org/~kvaneesh/gitweb.cgi?h=2.6.20-rc1-ci-to-linus;p=ci-to-linus.git;a=shortlog

http://git.openssi.org/~kvaneesh/gitweb.cgi?h=2.6.19-rc1-ci-to-linus;p=ci-to-linus.git;a=shortlog

-aneesh

      reply	other threads:[~2007-05-18 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 12:42 Ext4 Patch Queue using stgit Aneesh Kumar K.V
2007-05-18 13:23 ` 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 [this message]

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=464DDDDD.7080308@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.