On 2021-02-01 14:26, Marek Smetana via Cygwin-patches wrote:
I'm Sorry, this is my first patch using the mailing list.
I too struggled for ages getting these right;
first set up your ~/.gitconfig something like:
$ grep -v '^#' ~/.gitconfig
[user]
name = ...
email = ...
[sendemail]
bcc = ...
smtpServer = ...
confirm = always
[core]
editor = /usr/bin/gvim -f
When you commit your changes, the first line of the commit message becomes your
patch file name and email subject, so keep it < 63, leave a blank line, then
expand on the details in subsequent lines < 80, so I find it easier to run:
$ git diff @^ > COMMIT_MSG
hack away at that then:
$ git commit -F COMMIT_MSG ...
$ git format-patch --to=cygwin-patches@cygwin.com -1
which will write a file like:
0001-fhandler_serial.cc-MARK-and-SPACE-parity-for-serial-port.patch
hack away at that to improve it then:
$ git send-email --to=cygwin-patches@cygwin.com \
0001-fhandler_serial.cc-MARK-and-SPACE-parity-for-serial-port.patch
and answer the confirmation message if you enabled that above.
Does anyone know of a way to set different default patch email addresses for
newlib/ and winsup/ trees?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
