to attach, or not to attach?

[William Hubbs]

On Sun, Feb 14, 2010 at 04:02:40PM -0500, Storm Dragon wrote:
> Hi,
> Why not do both ways?

Because I don't think git send-email does that.  Here is an example of
how to create a patch to send to the list using git:

1) clone the repository.
2)  Make and commit your changes.  It would be best to commit to a local
branch.  Make sure to describe your changes in the commit message.
Typically the commit message should have a first line shorter than 50
characters as a summary of the change, then a blank line followed by a
more detailed description if necessary.  The detailed description should
be wrapped so that it is less than 80 characters wide.
3) use git send-email to send out your changes.  It emails the changes
out to the list in an inline message.

Changes sent out in this format are the easiest to apply to the tree.

Thanks,

William

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: 
<http://lists.freebsoft.org/pipermail/speechd/attachments/20100214/b116c999/attachment.pgp>