From: Andreas Ericsson <ae@op5.se>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org, ltuikov@yahoo.com
Subject: Re: [RFC/PATCH] git-reset to remove "$GIT_DIR/MERGE_MSG"
Date: Tue, 05 Dec 2006 09:36:30 +0100 [thread overview]
Message-ID: <45752F8E.9020405@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.63.0612050847340.28348@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Mon, 4 Dec 2006, Junio C Hamano wrote:
>
>> * Marked as RFC because I suspect I am missing a valid use case
>> where a user might want to say "reset" as part of continuing
>> the conflicted merge resolution, although I do not think of
>> any offhand...
>
> I can only speak for myself, of course: When I use git-reset in a merge,
> more often than not I use "--hard", in which case I want to try something
> different. So yes, I like this patch.
>
> The only possible exception I can think of: git-reset --mixed when a
> merge failed.
>
Indeed, but any invocation of git-reset means you'll quite likely have
to re-do the merge to get all changes anyways.
Like most others, I also use the --hard option most of the times when I
have merge-errors (usually because I've forgotten to create a
topic-branch to do my work in, so I create one from 'master', reset
master to whatever it was last time I pulled and then try rebase'ing on
to it).
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
next prev parent reply other threads:[~2006-12-05 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 3:44 [RFC/PATCH] git-reset to remove "$GIT_DIR/MERGE_MSG" Junio C Hamano
2006-12-05 6:19 ` Luben Tuikov
2006-12-05 8:22 ` Johannes Schindelin
2006-12-05 8:36 ` Andreas Ericsson [this message]
2006-12-05 9:03 ` Johannes Schindelin
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=45752F8E.9020405@op5.se \
--to=ae@op5.se \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=ltuikov@yahoo.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.