From: Ivan Kanis <expire-by-2011-02-20@kanis.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Adam Monsen <haircut@gmail.com>, git@vger.kernel.org
Subject: Re: configuring cherry-pick to always use -x?
Date: Tue, 15 Feb 2011 10:38:01 +0100 [thread overview]
Message-ID: <87vd0lwscm.fsf@kanis.fr> (raw)
In-Reply-To: <AANLkTimi=d0qbO3_-BEnPEJ+iy9B=_fksF7TiBE7HorC@mail.gmail.com> (Junio C. Hamano's message of "Mon, 14 Feb 2011 13:05:06 -0800")
Hi Junio,
Junio C Hamano <gitster@pobox.com> wrote:
> On Mon, Feb 14, 2011 at 9:19 AM, Adam Monsen <haircut@gmail.com> wrote:
>> Is there a configuration option to make cherry-pick always include the
>> source commit hash in the new commit log message?
>
> Not currently, but before we go any further, could you please justify
> in what workflow it would make sense to use -x most of the time?
>
> We used to add the "cherry-picked from" by default in the very early
> days, and stopped doing so for a reason, and also deliberately stayed
> away from adding such a configuration to actively discourage the use
> of -x without making the user thinking twice.
Could you elaborate on the reason why -x is a bad idea?
Kind regards,
--
Ivan Kanis, Release Manager, Vision Objects,
Tel +33 2 28 01 84 44, Fax +33 2 40 25 89 20
http://www.visionobjects.com
We meet no Stranger, but Ourself.
-- Emily Dickinson
prev parent reply other threads:[~2011-02-15 9:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 17:19 configuring cherry-pick to always use -x? Adam Monsen
2011-02-14 18:09 ` Jay Soffian
2011-02-14 21:23 ` Junio C Hamano
2011-02-14 21:05 ` Junio C Hamano
2011-02-14 21:50 ` Adam Monsen
2011-02-15 8:58 ` Michael J Gruber
2011-02-15 9:18 ` Jonathan Nieder
2011-02-15 9:29 ` Michael J Gruber
2011-02-15 16:16 ` Jay Soffian
2011-02-15 21:03 ` release maintenance vs. release engineering (was: configuring cherry-pick to always use -x?) Adam Monsen
2011-02-14 21:53 ` configuring cherry-pick to always use -x? Jay Soffian
2011-02-15 9:38 ` Ivan Kanis [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=87vd0lwscm.fsf@kanis.fr \
--to=expire-by-2011-02-20@kanis.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=haircut@gmail.com \
/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).