git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: stgit: editing description of patch
Date: Thu, 4 Oct 2007 12:45:17 -0400	[thread overview]
Message-ID: <9e4733910710040945l2335f3d7le6f45510640d3a6e@mail.gmail.com> (raw)
In-Reply-To: <20071004154836.GB21717@diana.vm.bytemark.co.uk>

On 10/4/07, Karl Hasselström <kha@treskal.com> wrote:
> I've never thought of the patch names as anything that would make
> sense to export from a repository (like reflogs), so using the first
> line of the commit message for mail subject (like git does) always
> seemed like a no-brainer. But then I don't have any experience using
> quilt or any related tool.

Why are the patch name and the short description independent
variables? Wouldn't it make more sense to treat these as a single
unified item? If I rename the patch it would automatically edit the
first line of the description, etc...

When importing a patch from a saved email, stg should strip all the
email headers out of the description. I have to manually fix that up.

-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2007-10-04 16:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 23:26 stgit: editing description of patch Jon Smirl
2007-10-04  2:14 ` Jon Smirl
2007-10-04  8:26   ` Karl Hasselström
2007-10-04 13:16     ` Jon Smirl
2007-10-04 15:48       ` Karl Hasselström
2007-10-04 16:45         ` Jon Smirl [this message]
2007-10-04 17:39           ` Karl Hasselström
2007-10-05  9:16             ` Catalin Marinas

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=9e4733910710040945l2335f3d7le6f45510640d3a6e@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.com \
    /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).