From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH v3 00/10] replace: add option to edit a Git object
Date: Mon, 19 May 2014 13:39:19 -0700 [thread overview]
Message-ID: <xmqqr43py03s.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140517120649.27582.58609.chriscool@tuxfamily.org> (Christian Couder's message of "Sat, 17 May 2014 14:16:29 +0200")
Christian Couder <chriscool@tuxfamily.org> writes:
> This patch series comes from what Peff sent in the following thread:
>
> http://thread.gmane.org/gmane.comp.version-control.git/243361/focus=243528
>
> The only changes compared to v2 are in the test (8/10) and documentation
> patches (10/10). Thanks to Peff.
>
> Christian Couder (6):
> replace: make sure --edit results in a different object
> replace: refactor checking ref validity
> replace: die early if replace ref already exists
> replace: add tests for --edit
> replace: add --edit to usage string
> Documentation: replace: describe new --edit option
>
> Jeff King (4):
> replace: refactor command-mode determination
> replace: use OPT_CMDMODE to handle modes
> replace: factor object resolution out of replace_object
> replace: add --edit option
Part of this is already in 'next'; I'd assume that the first four
can be discarded and it is safe to queue only the remaining six on
top of what we already have.
Thanks.
prev parent reply other threads:[~2014-05-19 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 12:16 [PATCH v3 00/10] replace: add option to edit a Git object Christian Couder
2014-05-17 12:16 ` [PATCH v3 01/10] replace: refactor command-mode determination Christian Couder
2014-05-17 12:16 ` [PATCH v3 02/10] replace: use OPT_CMDMODE to handle modes Christian Couder
2014-05-17 12:16 ` [PATCH v3 03/10] replace: factor object resolution out of replace_object Christian Couder
2014-05-17 12:16 ` [PATCH v3 04/10] replace: add --edit option Christian Couder
2014-05-17 12:16 ` [PATCH v3 05/10] replace: make sure --edit results in a different object Christian Couder
2014-05-17 12:16 ` [PATCH v3 06/10] replace: refactor checking ref validity Christian Couder
2014-05-17 12:16 ` [PATCH v3 07/10] replace: die early if replace ref already exists Christian Couder
2014-05-17 12:16 ` [PATCH v3 08/10] replace: add tests for --edit Christian Couder
2014-05-17 12:16 ` [PATCH v3 09/10] replace: add --edit to usage string Christian Couder
2014-05-17 12:16 ` [PATCH v3 10/10] Documentation: replace: describe new --edit option Christian Couder
2014-05-19 20:39 ` Junio C Hamano [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=xmqqr43py03s.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.