From: Junio C Hamano <gitster@pobox.com>
To: Eugene Sajine <euguess@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [FEATURE REQUEST] - extend git request-pull to send email
Date: Thu, 03 Feb 2011 15:06:53 -0800 [thread overview]
Message-ID: <7vlj1wzpiq.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vpqr8zpux.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu\, 03 Feb 2011 14\:59\:34 -0800")
Junio C Hamano <gitster@pobox.com> writes:
>> What do you think?
>
> Horrible ;-).
Just a quick note.
Please take this with a huge grain of salt, considering that the comment
is coming from somebody who thinks --compose and format-patch integration
to git-send-email was also a bad idea.
next prev parent reply other threads:[~2011-02-03 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 22:35 [FEATURE REQUEST] - extend git request-pull to send email Eugene Sajine
2011-02-03 22:59 ` Junio C Hamano
2011-02-03 23:06 ` Junio C Hamano [this message]
2011-02-03 23:30 ` Eugene Sajine
2011-02-03 23:34 ` Eugene Sajine
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=7vlj1wzpiq.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
/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).