This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: How to properly send patches
- From: Stefan Wallentowitz <stefan at wallentowitz dot de>
- To: newlib at sourceware dot org
- Date: Sun, 10 Apr 2016 22:57:26 +0200
- Subject: Re: How to properly send patches
- Authentication-results: sourceware.org; auth=none
- References: <CAFvk=0ssrKLYpQVJt4rS8o8WM_xo82zL6-KbooYNfJoJe+h11A at mail dot gmail dot com> <20160407175341 dot GT6588 at vapier dot lan> <20160408083522 dot GB7505 at calimero dot vinschen dot de> <20160408200944 dot GD6588 at vapier dot lan> <CAFvk=0ukqXegcmPuAY6Tb+k85gQA1hSeSAKZnritwYaiPdNpTg at mail dot gmail dot com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10.04.2016 20:24, Jakub Sejdak wrote:
> There is also one more thing - we were internally working on some
> "copy" of newlib-cygwin repository on our server, where we could
> freely create branches, commit and push. Now I just applied
> everything we have to my local clone of newlib-cygwin as one
> commit. So format-patch will actually create one enormous patch. I
> was looking for a way to create one patch per new file (even in the
> same commit), but this will still generate ~150 email notifications
> for everyone one the mailing list. So final question: multiple
> small patches and many emails or just one copressed patch?
Hi,
just a quick hint: you will most probably run into the mailing list
size limit with one patch, a situation I circumvented for the OpenRISC
port initial patch by sending a link:
https://sourceware.org/ml/newlib/2015/msg00016.html
Cheers,
Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlcKvjYACgkQuMYtsrn2U9wE0gCcC7CWz/pulcZS3YN3Ts4LOMbQ
ZX8Anj1R47s49EzFpyaa1qi8yPBMY4Gu
=1qpf
-----END PGP SIGNATURE-----