submitting patches (was: Add Additional Column to Register Report (PATCH INCLUDED))
warlord at MIT.EDU
Mon Jun 30 09:23:00 EDT 2008
Christian Stimming <stimming at tuhh.de> 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.
I suppose this should be documented somewhere if it isn't
already. I haven't looked.
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord at MIT.EDU PGP key available
More information about the gnucash-devel