Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi,

On 2010-09-28, at 19:45, Nick Savage wrote:

I had the same problem. I used git to generate a patch file, and then
sent it in, and the email was much too long to be accepted, so I am
interested in how to do this as well.

I believe Git practice is if you can describe your change in 50 characters or less, it’s fine as a 
single patch. If not, split it up. If you have the former case–patch that makes sense as a single 
file but still too big for email–then you can (1) file a bug report and attach the patch to that, 
or (2) have a public Git repo on e.g. GitHub and email the list asking devs to pull your changes.

Yawar
 

Attachment: PGP.sig
Description: This is a digitally signed message part


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.