From: Junio C Hamano <gitster@pobox.com>
To: Dan Johnson <computerdruid@gmail.com>
Cc: Peter Jones <pjones@redhat.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-am: Handle "git show" output correctly
Date: Wed, 12 Sep 2012 16:05:19 -0700 [thread overview]
Message-ID: <7v4nn2c05s.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAPBPrntXCDHwWkYV3pnj3+d8FCZCmEVPHkSxyVg0Jzd0tzZsGA@mail.gmail.com> (Dan Johnson's message of "Wed, 12 Sep 2012 18:31:03 -0400")
Dan Johnson <computerdruid@gmail.com> writes:
> I was assuming Peter would accept the patch, and reply with a "in the
> future, please submit the output of format-patch", thus correcting the
> submitter's behavior. This warning would serve someone who did not
> know that they wanted the output of format-patch, and hopefully teach
> them to send such a reply message.
"Next time, please do this" rarely has worked in practice. This is
because the moment you accepted the current patch, you have already
lost the "carrot" ;-)
next prev parent reply other threads:[~2012-09-12 23:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 15:26 [PATCH] Handle "git show" output correctly Peter Jones
2012-09-12 15:30 ` Peter Jones
2012-09-12 15:41 ` Matthieu Moy
2012-09-12 15:49 ` [PATCH] [git-am] " Peter Jones
2012-09-12 15:57 ` Matthieu Moy
2012-09-12 17:32 ` Junio C Hamano
2012-09-12 18:05 ` Peter Jones
2012-09-12 19:07 ` Junio C Hamano
2012-09-12 15:42 ` [PATCH] " Peter Jones
2012-09-12 15:40 ` Matthieu Moy
2012-09-12 18:00 ` Peter Jones
2012-09-12 18:08 ` [PATCH] git-am: " Peter Jones
2012-09-12 20:06 ` Junio C Hamano
2012-09-12 20:48 ` Peter Jones
2012-09-12 21:03 ` Peter Jones
2012-09-12 21:18 ` Junio C Hamano
2012-09-12 21:26 ` Dan Johnson
2012-09-12 22:19 ` Junio C Hamano
2012-09-12 22:31 ` Dan Johnson
2012-09-12 23:05 ` Junio C Hamano [this message]
2012-09-12 22:41 ` Andreas Ericsson
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=7v4nn2c05s.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=computerdruid@gmail.com \
--cc=git@vger.kernel.org \
--cc=pjones@redhat.com \
/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).