git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
To: git@vger.kernel.org
Subject: git send-email should always ask for in-reply-to
Date: Tue, 1 Jun 2010 16:41:12 +0200	[thread overview]
Message-ID: <201006011641.12401.alexander.stein@informatik.tu-chemnitz.de> (raw)

Hi,

i currently have the problem that, if I set sendemail.from and sendemail.to in 
git-config (from global and to project-specific but that doesn't matter) git 
send-email doesn't ask me for a in-reply-to message-ID. I set these 2 config 
options for convenience. But i also want to specify a message-id after calling 
git send-email to get a proper thread on the mailing list.
I dived into git-send-email.perl and found $prompting which is only != 0 if 
$sender or @to isn't already set (lines 672-685). On line 706-709 there are 
some check whether $initial_reply_to should be asked or not. If $prompting is 
sitll 0 $initial_reply_to will not be asked.
In my opinion git send-email should always ask for in-reply-to. I know there 
is --in-reply-to option but this keeps me from using the git command from 
shell history as i have to modify the parameter each time.

What do you think about it?
Best regards
Alexander

             reply	other threads:[~2010-06-01 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 14:41 Alexander Stein [this message]
2010-06-01 15:46 ` git send-email should always ask for in-reply-to 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

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=201006011641.12401.alexander.stein@informatik.tu-chemnitz.de \
    --to=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).