From: Theodore Tso <tytso@mit.edu>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 Patch Queue using stgit.
Date: Fri, 18 May 2007 12:06:26 -0400 [thread overview]
Message-ID: <20070518160626.GA19911@thunk.org> (raw)
In-Reply-To: <464D9F2F.3030904@linux.vnet.ibm.com>
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.
Regards,
- Ted
next prev parent reply other threads:[~2007-05-18 16:06 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 [this message]
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=20070518160626.GA19911@thunk.org \
--to=tytso@mit.edu \
--cc=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