On Thu, Jul 10, 2014 at 7:36 PM, Junio C Hamano gits...@pobox.com wrote:
Junio C Hamano gits...@pobox.com writes:
As the user might expect that a new replace ref was created on success
(0 exit code), and as we should at least warn if we would create a
commit that is the same as an existing
Christian Couder christian.cou...@gmail.com writes:
On Thu, Jul 10, 2014 at 7:36 PM, Junio C Hamano gits...@pobox.com wrote:
Making sure A's parent is B would be an
idempotent operation, no? Why not just make sure A's parent is
already B and report Your wish has been granted to the user?
On Fri, Jul 11, 2014 at 4:22 PM, Junio C Hamano gits...@pobox.com wrote:
Christian Couder christian.cou...@gmail.com writes:
On Thu, Jul 10, 2014 at 7:36 PM, Junio C Hamano gits...@pobox.com wrote:
Making sure A's parent is B would be an
idempotent operation, no? Why not just make sure A's
Christian Couder christian.cou...@gmail.com writes:
On Fri, Jul 11, 2014 at 4:22 PM, Junio C Hamano gits...@pobox.com wrote:
Christian Couder christian.cou...@gmail.com writes:
On Thu, Jul 10, 2014 at 7:36 PM, Junio C Hamano gits...@pobox.com wrote:
Making sure A's parent is B would be an
On Fri, Jul 11, 2014 at 11:25:43AM -0700, Junio C Hamano wrote:
Christian Couder christian.cou...@gmail.com writes:
On Fri, Jul 11, 2014 at 4:22 PM, Junio C Hamano gits...@pobox.com wrote:
Christian Couder christian.cou...@gmail.com writes:
On Thu, Jul 10, 2014 at 7:36 PM, Junio C
On Wed, Jul 9, 2014 at 4:59 PM, Junio C Hamano gits...@pobox.com wrote:
Christian Couder chrisc...@tuxfamily.org writes:
+static void replace_parents(struct strbuf *buf, int argc, const char **argv)
+{
+ struct strbuf new_parents = STRBUF_INIT;
+ const char *parent_start,
Christian Couder christian.cou...@gmail.com writes:
Is this really an error? It may be a warning-worthy situation for a
user or a script to end up doing a no-op graft, e.g.
git replace --graft HEAD HEAD^
but I wonder if it is more convenient to signal an error (like this
patch
Junio C Hamano gits...@pobox.com writes:
Christian Couder christian.cou...@gmail.com writes:
Is this really an error? It may be a warning-worthy situation for a
user or a script to end up doing a no-op graft, e.g.
git replace --graft HEAD HEAD^
but I wonder if it is more
Christian Couder chrisc...@tuxfamily.org writes:
The usage string for this option is:
git replace [-f] --graft commit [parent...]
First we create a new commit that is the same as commit
except that its parents are [parents...]
Then we create a replace ref that replace commit with
the
9 matches
Mail list logo
