Jeremy Katz wrote:
> Note that if it's a single patch, --compose is probably overkill as
> it makes two messages rather than one. Your commit message is
> self-explanatory, no? (... and if not, edit the 0001 file before
> running git send-email)
For bonus points, the --subject-prefix option to g
On Thursday, March 12 2009, Jesse Keating said:
> Here is a message from git send-email.
>
> To get here, I used:
>
> $ git commit -a
> Created commit cb85f54: Disable rawhide.
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> $ git format-patch HEAD^
> 0001-Disable-rawhide.patch
>
> $ gi
Here is a message from git send-email.
To get here, I used:
$ git commit -a
Created commit cb85f54: Disable rawhide.
1 files changed, 2 insertions(+), 1 deletions(-)
$ git format-patch HEAD^
0001-Disable-rawhide.patch
$ git send-email --compose --to Fedora-infrastructure-list@redhat.com
0001-
