On Fri, Oct 9, 2020 at 3:51 AM Thomas Zimmermann tzimmermann@suse.de wrote:
Hi
Am 09.10.20 um 09:38 schrieb Sandeep Raghuraman:
On 10/9/20 12:44 PM, Thomas Zimmermann wrote:
Hi
Am 09.10.20 um 08:47 schrieb Thomas Zimmermann:
NACK for the entire lack of any form of commit description.
Please see the documentation at [1] on how to describe the changes and getting your patches merged.
Yes, I tried to use git send-email to send patches this time, and it resulted in this disaster. I'll stick to sending them through Thunderbird.
What's the problem with send-email?
A typical call for your patchset would look like
git send-mail <upstream-branch>...HEAD --cover-letter --annotate --to=... --cc=...
That allows you to write the cover letter and have it sent out. IIRC you need ot set $EDITOR to your favorite text editor; and configure the SMTP server in ~/.gitconfig, under [sendemail].
You can also do `git format-patch -3 --cover-letter` and manually edit the coverletter as needed then send them with git send-email.
Alex
Best regards Thomas
Best regards Thomas
[1]
dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
-- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel