From: Jing Xue <jingxue@digizenstudio.com>
To: git <git@vger.kernel.org>
Subject: git-send-email doesn't like me+git ML
Date: Thu, 13 Dec 2007 20:47:53 -0500 [thread overview]
Message-ID: <20071214014753.GB8914@fawkes> (raw)
OK, this is bewildering. I tried a couple of times sending a trivial
patch (the one that makes git-stash show keep quiet when there aren't
any stashes), but it never made it to the list every time I used
git-send-email, yet as soon as I did it as a regular email, i.e.,
starting a new message in mutt, pasting the patch into the body, and
sending it, it worked just fine.
My mail log shows the mails (the one thru git-send-email) went out just
fine. And it always worked when I tried to use git-send-email to send
the patch to my gmail address. It just doesn't work with the list - and
that obviously can't be. 8-)
--
Jing Xue
next reply other threads:[~2007-12-14 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 1:47 Jing Xue [this message]
2007-12-14 8:54 ` git-send-email doesn't like me+git ML Andreas Ericsson
2007-12-15 5:20 ` Jing Xue
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=20071214014753.GB8914@fawkes \
--to=jingxue@digizenstudio.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).