From: Michael J Gruber <git@drmicha.warpmail.net>
To: Miles Bader <miles@gnu.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Snipping on this list (Was: Re: [PATCHv2 3/3] git-add: rename -u to -a)
Date: Mon, 28 Feb 2011 10:05:08 +0100 [thread overview]
Message-ID: <4D6B6544.2040404@drmicha.warpmail.net> (raw)
In-Reply-To: <buohbbo35g8.fsf@dhlpc061.dev.necel.com>
Miles Bader venit, vidit, dixit 28.02.2011 09:53:
> Michael J Gruber <git@drmicha.warpmail.net> writes:
>> And would you please try and follow our netiquete here? I had promised
>> myself not to respond any more, but see how I'm still forgiving. Try and
>> deserve it :)
>
> I'm confused; how am I "not following netiquete"? It was an honest
> question...
Well, we're trying to cut as little as possible here. In particular,
don't just include one single line, taking it completely out of context.
Even more particularly, don't cut away the paragraph leading to a
conclusion when you're responding that conclusion - in this case that
paragraph would have ansered your question already. (And I don't think
I'm saying this the first time, but I'm used to it - I have little kids...).
We do cut patches when we respond to a commit message only (and the
response is not about the implementation), or hunks of a patch when
they're not related to the response.
As a general guideline, a reader should be able to understand the
response without looking up the post you are responding to (but may have
to read up on a longer thread). When in doubt, err on the lenient side
(less cutting), and make your MUA display quotes nicely (conversation
view, quotecollapse, ...).
And don't cull cc, don't break the thread. (You haven don't that here, I
do appreciate that, thanks!).
Cheers,
Michael
next prev parent reply other threads:[~2011-02-28 9:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 14:45 [PATCH/RFC 0/3] add/commit -u/-a/-A Michael J Gruber
2011-02-25 14:45 ` [PATCH/RFC 1/3] git-add: make -A description clearer vs. -u Michael J Gruber
2011-02-25 19:04 ` Junio C Hamano
2011-02-25 14:45 ` [PATCH/RFC 2/3] git-commit: rename --all to --track Michael J Gruber
2011-02-25 19:08 ` Junio C Hamano
2011-02-25 14:45 ` [PATCH/RFC 3/3] git-add: rename -u to -a Michael J Gruber
2011-02-25 19:40 ` Junio C Hamano
[not found] ` <7vr5aw9b7m.fsf@alter.siamese.dyndns.org>
2011-02-26 10:30 ` [PATCH/RFC 0/3] add/commit -u/-a/-A Michael J Gruber
2011-02-27 15:50 ` [PATCHv2 " Michael J Gruber
2011-02-27 15:50 ` [PATCHv2 1/3] git-add: make -A description clearer vs. -u Michael J Gruber
2011-02-27 23:35 ` Junio C Hamano
2011-02-27 15:50 ` [PATCHv2 2/3] git-commit: rename --all to --all-tracked Michael J Gruber
2011-02-27 15:50 ` [PATCHv2 3/3] git-add: rename -u to -a Michael J Gruber
2011-02-27 16:38 ` Nguyen Thai Ngoc Duy
2011-02-28 6:40 ` Junio C Hamano
2011-02-28 8:30 ` Michael J Gruber
2011-02-28 8:42 ` Miles Bader
2011-02-28 8:46 ` Michael J Gruber
2011-02-28 8:53 ` Miles Bader
2011-02-28 9:05 ` Michael J Gruber [this message]
2011-02-28 18:18 ` Snipping on this list Junio C Hamano
2011-02-28 9:03 ` [PATCHv2 3/3] git-add: rename -u to -a Miles Bader
2011-02-28 9:08 ` Michael J Gruber
2011-02-28 9:40 ` Matthieu Moy
2011-02-28 9:49 ` Michael J Gruber
2011-02-28 10:01 ` Tor Arntsen
2011-02-28 10:03 ` Michael J Gruber
2011-02-28 10:05 ` Matthieu Moy
2011-02-28 10:53 ` Michael J Gruber
2011-02-28 18:21 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6B6544.2040404@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=miles@gnu.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).