+1, no comments.
;-) D.
On 9/24/2010 12:04 PM, Brice Figureau wrote:
On Thu, 2010-09-23 at 18:27 -0700, Jacob Helwig wrote:
Actually, for me, it's harder to top-post, since my mail client is setup
to automatically put me just above my signature (below the quoted email)
when composing. ;-)
I feel the same.
If it's standard practice, because that's what we want, then I'll change
what I do. If it's standard practice because most people are using the
gmail web interface, and are lazy... ;-) So...in light of what appear
to be a number of ambiguities in our processes, as of late: Should I
actually change what I'm doing, or were you just trying to save me some
effort? (Top-posted, assuming the former.)
I myself largely prefer bottom-posting for discussion thread like this
one. But top-most make sense for patches, since you wan't your answer to
be noticed at first glance (ie without to scroll page long).
Of course code comments should be inlined in the patch.
If I had to choose a convention:
* discussion thread: bottom-post with proper off-context text
elimination respecting attributions
* patch code reviews: answer at top, code review inlined
My 0.02$
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to puppet-...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
