From: Chris Webb <chris@arachsys.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] cherry-pick: add --allow-empty-message option
Date: Mon, 6 Aug 2012 12:00:16 +0100 [thread overview]
Message-ID: <20120806110016.GA8587@arachsys.com> (raw)
In-Reply-To: <20120806105729.GC16873@hmsreliant.think-freely.org>
Neil Horman <nhorman@tuxdriver.com> writes:
> Having read over this thread, I think this is definately the way to go. As
> discussed having cherry-pick stop and give the user a chance to fix empty
> history messages by default, and providing a switch to override that behavior
> makes sense to me. That said, shouldn't there be extra code here in the rebase
> scripts to automate commit migration in that path as well?
Yes, this patch just adds the support to the low-level git cherry-pick as
you say. I'll follow up with a patch to use the new feature in rebase [-i]
when I get some free time, hopefully later this week.
Cheers,
Chris.
next prev parent reply other threads:[~2012-08-06 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 11:16 Cherry-picking commits with empty messages Chris Webb
2012-08-01 17:52 ` Junio C Hamano
2012-08-01 18:15 ` Angus Hammond
2012-08-01 22:26 ` Junio C Hamano
2012-08-02 10:10 ` Angus Hammond
2012-08-02 8:55 ` Chris Webb
2012-08-02 10:38 ` [PATCH] cherry-pick: add --allow-empty-message option Chris Webb
2012-08-06 10:57 ` Neil Horman
2012-08-06 11:00 ` Chris Webb [this message]
2012-08-06 11:11 ` Neil Horman
2012-08-03 0:22 ` Cherry-picking commits with empty messages Neil Horman
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=20120806110016.GA8587@arachsys.com \
--to=chris@arachsys.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nhorman@tuxdriver.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.
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.