to attach, or not to attach?

[Storm Dragon]

Hi,
Why not do both ways?
Storm


-- 
Follow me on Twitter:
http://www.twitter.com/stormdragon2976
My blog, Thoughts of a Dragon:
http://www.stormdragon.us/
What color dragon are you?
http://quizfarm.com/quizzes/new/alustriel07/what-color-dragon-would-you-be/



On Mon, 2010-02-15 at 07:58 +1100, Luke Yelavich wrote:

> On Sun, Feb 14, 2010 at 11:09:28PM EST, Chris Brannon wrote:
> > Halim Sahin wrote:
> > > Hi,
> > > Thx for you work but please can you send the patches as attachmnent?
> > 
> > I basicly concur with William on this issue,
> > for the following three reasons.
> > 
> > 1. Inline patches are easier to review.
> > 2. They are customary in many git-using email-based communities, notably
> > the Linux Kernel Mailing List.
> > 3. By default, git format-patch gives inline patches.
> > Three is likely a corollary of two.
> > 
> > There is one good counter-argument against inlining.
> > If some list members are using a version control system other than git, then
> > they will have an easier time with attachments.
> 
> I personally agree. I simply need to save the patch emails to a patches box, 
> and run git am over that box.
> 
> Luke
> 
> _______________________________________________
> Speechd mailing list
> Speechd at lists.freebsoft.org
> http://lists.freebsoft.org/mailman/listinfo/speechd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.freebsoft.org/pipermail/speechd/attachments/20100214/573f254c/attachment.htm>