Derek Atkins wrote: > Christian Stimming <[EMAIL PROTECTED]> writes: > > >> Am Freitag, 27. Juni 2008 18:07 schrieb Derek Atkins: >> >>> Always attach patches. It's just common knowledge. >>> >> That's what I thought, too - until I submitted my first patch to any of the >> git mailing lists. Folks over there are pushing very very hard for inlined >> patches instead of attached ones. Their main reason is that they'd like to >> reply and quote the relevant patch portions directly. >> >> As always, there are reasons for both ways of doing things. I'd just like to >> reply here that indeed each project has different preferences in this >> question, and in fact both preferences exist in the free software world. >> > > Very interesting! Inlined patches are very hard to apply, > but eh, to each their own. > The gcc development community also inlines patches in their messages. I thought patch would ignore all the mail junk at the top of a message until it saw something that looks like a patch, so applying should be a matter of saving the message and applying the resulting file.
Jerry _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
