On 2008-01-25 09:57:50 -0500, Jon Smirl wrote:
> 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.
I don't think we need to get quite that fancy. Wouldn't it suffice to
have a --cover-file=<filename> option to stg mail, and if both
--cover-file and --edit-cover were given, update that file with new
diffstat etc?
And per-branch config options if you want to set these permanently, of
course.
> 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.
Patches without cover letters can also have versions, so I don't think
associating versions with cover letters is a splendid idea, but I get
your point.
I guess a solution much like the one for cover letters would work
here. A separate file, and command-line and config options to point to
it.
> I didn't know I wanted features like this until I made a patch that
> has gone through 25 versions.
Your feedback is much appreciated. Keep at it!
--
Karl Hasselström, kha@xxxxxxxxxxx
www.treskal.com/kalle
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
