[Zlib-devel] zlib 1.2.5.1 baseline
Mark Brown
broonie at sirena.org.uk
Mon Sep 12 06:47:07 EDT 2011
On Sun, Sep 11, 2011 at 11:45:20AM -0700, Mark Adler wrote:
> My point is, to the extent that I understand git send-mail (I'm new to
> this git stuff), you don't get to edit the email message that is sent.
> You issue the command and boom, off it goes. All that is sent is the
> information included in the commit. Right?
You can edit if you like. You can also do a separate git format-patch
stage, edit the mails, then do the send-email on the edited patches.
> My preference (not demand) is that the patches be in an email with
> something you write preceding it that provides some context to the
> group. Like why these patches should be included, what motivated you
> to write these patches, that I should ignore the last seven similar
For standalone patches the general approach most projects using git take
is to require that this stuff actually be in the commit message; if you
can't tell why the patch is a good idea from there it tends to mean that
the git history isn't great anyway.
More information about the Zlib-devel
mailing list