From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: stgit: per branch cover letters
Date: Fri, 25 Jan 2008 09:57:50 -0500 [thread overview]
Message-ID: <9e4733910801250657p2d7fdc66o8a631d7587125949@mail.gmail.com> (raw)
It would be convenient to have per branch cover letters that are
stored by stg and get automatically applied when a patch set is
mailed. Use 'stg edit' to alter them. The first time you email a
series you would get an editor to write the cover letter if you hadn't
already done it. You could track the "to=" this way also.
Another useful feature would be a config option that says something
like "prompt for new version" when mailed. Now each time you mail the
series it throws you into the cover page editor with an incremented
patch version. You can just quit out of the editor if you don't want
to increment the version.
I didn't know I wanted features like this until I made a patch that
has gone through 25 versions.
--
Jon Smirl
jonsmirl@gmail.com
next reply other threads:[~2008-01-25 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 14:57 Jon Smirl [this message]
2008-01-25 16:46 ` stgit: per branch cover letters Karl Hasselström
2008-01-25 17:03 ` Jon Smirl
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=9e4733910801250657p2d7fdc66o8a631d7587125949@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).