From: Jeremy White <jwhite@codeweavers.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: RFC re Thunderbird + imap-send
Date: Tue, 10 Feb 2009 13:00:57 -0600 [thread overview]
Message-ID: <4991CEE9.8040402@codeweavers.com> (raw)
In-Reply-To: <49915FB6.8010803@drmicha.warpmail.net>
> Looks okay here. I leave the tarring and feathering to Dscho ;)
Thanks.
>
> Trying this out showed that indeed git-imap-send needs much more love.
> The man page doesn't say much, doesn't describe all options. Most
> options can be specified in config only. You can't pass file arguments,
> only stdin. You can't even pass a recipient!
Hmm. I think the documentation/man page is correct, at least in the
tip; Rob Shearman fixed it back in July.
I think your larger concerns about git-imap-send are valid; it does seem
that having two paths for emailing patches is less than ideal.
But I'm going to cowardly claim that is outside of my scope at this
point. (I like starting flame wars and all, but adding --html to
git-send-email just seems like a poor choice for my health <grin>).
Cheers,
Jeremy
prev parent reply other threads:[~2009-02-10 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 21:49 RFC re Thunderbird + imap-send Jeremy White
2009-02-10 11:06 ` Michael J Gruber
2009-02-10 12:24 ` Ben Bucksch
2009-02-10 13:23 ` Jeremy White
2009-02-10 19:00 ` Jeremy White [this message]
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=4991CEE9.8040402@codeweavers.com \
--to=jwhite@codeweavers.com \
--cc=git@drmicha.warpmail.net \
--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).