From: Timur Tabi <timur@freescale.com>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org
Subject: Re: git-send-email --suppress-from option doesn't work.
Date: Thu, 25 Jan 2007 10:47:32 -0600 [thread overview]
Message-ID: <45B8DF24.6080001@freescale.com> (raw)
In-Reply-To: <45B01DD4.7000204@op5.se>
Andreas Ericsson wrote:
>
> I believe
>
> (/^(Cc|From):[^<]+<([^>])+>.*$/)
>
> would do the trick for your case. It would however fail when specifying a proper
> --from address in the 'git commit --author="Foo Barson <foo@barson.com>"' style.
Even so, it would still be very picky about the layout. --suppress-from should
just compare the actual email addresses, not the names or any other characters.
> Are you sure you need to specify --from for those patches though?
Yes. If I don't specify --from, then git-send-email will prompt me for the
From: address. I want git-send-email to be completely non-interactive.
>> Some of you might say at this point, "Why don't you just specify --from
>> "Timur Tabi <timur@freescale.com>"? I tried that, and it still doesn't
>> work.
>
> That sounds extremely odd indeed. Could this have to do with character
> conversion?
Actually, I figured out the problem is that I can't do this:
FROM='--from "Foo Barson <foo@barson.com>"'
git-send-email $FROM ...
I got all sorts of weird messages about unbalanced > or something. Instead, I
need to do this:
FROM="Foo Barson <foo@barson.com>"
git-send-email --from $FROM ...
This is probably a shell issue instead of a git-send-email issue, but it is
annoying.
--
Timur Tabi
Linux Kernel Developer @ Freescale
prev parent reply other threads:[~2007-01-25 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 21:07 git-send-email --suppress-from option doesn't work Timur Tabi
2007-01-19 1:24 ` Andreas Ericsson
2007-01-25 16:47 ` Timur Tabi [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=45B8DF24.6080001@freescale.com \
--to=timur@freescale.com \
--cc=ae@op5.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.