Re: [PATCH v3 00/10] replace: add option to edit a Git object
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 19, 2014, 20:39 UTC
- Message-ID
- <xmqqr43py03s.fsf@gitster.dls.corp.google.com>
- In-Reply-To
- <20140517120649.27582.58609.chriscool@tuxfamily.org>
Christian Couder <chriscool@tuxfamily.org> writes:
Show 20 quoted lines
> 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.