From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] send-email: Ask for in-reply message ID even if from and to is already known
Date: Fri, 11 Jun 2010 00:28:58 +0200 [thread overview]
Message-ID: <vpqpqzyzfmd.fsf@bauges.imag.fr> (raw)
In-Reply-To: <1275415730-15360-1-git-send-email-alexander.stein@informatik.tu-chemnitz.de> (Alexander Stein's message of "Tue\, 1 Jun 2010 20\:08\:50 +0200")
Alexander Stein <alexander.stein@informatik.tu-chemnitz.de> writes:
> This patch removes the prompting variable so git send-email always asks
> for a in-reply message ID (unless specified on command line) even when
> sendemail.from and sendemail.to is set in ~/.gitconfig or .git/config
Does this mean there's no way to run send-email non-interactively
without a reply-to?
I do want to get the prompt even though I want to set the sender field
in my ~/.gitconfig, but I wouldn't want the prompt to appear in the
cron job I run every nights to send me new patches in some repo for
example (a change in git-send-email already broke it in the past,
that's a rather anoying failure).
You probably want an option to enable/disable prompting. I'm not sure
whether it should be opt-in or opt-out.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
prev parent reply other threads:[~2010-06-10 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 14:41 git send-email should always ask for in-reply-to Alexander Stein
2010-06-01 15:46 ` Matthieu Moy
2010-06-01 18:08 ` [PATCH] send-email: Ask for in-reply message ID even if from and to is already known Alexander Stein
2010-06-10 17:08 ` Alexander Stein
2010-06-10 17:18 ` Ævar Arnfjörð Bjarmason
2010-06-11 19:06 ` Junio C Hamano
2010-06-11 20:11 ` Alexander Stein
2010-06-10 22:28 ` Matthieu Moy [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqpqzyzfmd.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=alexander.stein@informatik.tu-chemnitz.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).