From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@MIT.EDU>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH] e2fsprogs: fix ext2fs_extent_get for uninit leaf extents
Date: Thu, 20 Mar 2008 16:04:47 -0500 [thread overview]
Message-ID: <47E2D16F.2010407@redhat.com> (raw)
In-Reply-To: <20080320202025.GM13719@mit.edu>
Theodore Tso wrote:
> On Wed, Mar 19, 2008 at 03:20:18PM -0500, Eric Sandeen wrote:
>> Fix ext2fs_extent_get for uninit leaf extents
>>
>> From: Eric Sandeen <sandeen@redhat.com>
>
> I'm guessing you used git-format-patch but not git-send-mail to send
> out the patch? Not a big deal, but it meant I had to do a "git commit
> --amend" to edit out the aboe two lines after doing a "git am".
>
> Suggested workflow that results in a nice patch series being sent to
> linux-ext4, as well as making it easy for a maintainer using git to
> suck it into git:
Thanks... I'm still embarassingly git-illiterate. Will do better next
time :)
-Eric
> % git-format-patch -n --subject-prefix="PATCH, E2FSPROGS" -o /tmp/to-send master
>
> This creates the patch series for all commits starting at the
> branch master (substitute next if you are basing your
> development branch off of next, etc.), and places the results
> in the directory /tmp/to-send, which will be created if it
> doesn't exist. It will use the first line of the commit log
> as the subject line, prefixed with [I/N PATCH, E2FSPROGS],
> where I/N will be 1/10, 2/10, 3/10, etc. "Git am" will take
> the subject, strip out what is in square brackets and use that
> as the first line of the commit log.
>
> % git-send-email --to=linux-ext4@vger.kernel.org /tmp/to-send
>
> This will send the patches found in /tmp/to-send to
> linux-ext4@vger.kernel.org, appropritaely formated. If you
> want to add an introductory message, add the option --compose
> to the above command-line. If you want to make the patch
> series be a reply to some message thread, just note the
> Message-ID of the message you want to reply to, and just copy
> and paste it into git-send-email when it prompts you to do so.
> If you want the patch series to start a new thread, just hit
> return when the program prompts you for a In-Reply-To message-ID.
>
> Anyway, I've applied the patch and it's in the e2fsprogs tree. Thanks
> for noticing it!
>
> - Ted
prev parent reply other threads:[~2008-03-20 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 20:20 [PATCH] e2fsprogs: fix ext2fs_extent_get for uninit leaf extents Eric Sandeen
2008-03-20 20:20 ` Theodore Tso
2008-03-20 21:04 ` Eric Sandeen [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=47E2D16F.2010407@redhat.com \
--to=sandeen@redhat.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).