From: Luben Tuikov <ltuikov@yahoo.com>
To: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Cc: ltuikov@yahoo.com
Subject: Re: [RFC/PATCH] git-reset to remove "$GIT_DIR/MERGE_MSG"
Date: Mon, 4 Dec 2006 22:19:02 -0800 (PST) [thread overview]
Message-ID: <953031.74197.qm@web31806.mail.mud.yahoo.com> (raw)
In-Reply-To: <7v4psbknvb.fsf@assigned-by-dhcp.cox.net>
--- Junio C Hamano <junkio@cox.net> wrote:
> An earlier commit a9cb3c6e changed git-commit to use the
> contents of MERGE_MSG even when we do not have MERGE_HEAD (the
> rationale is in its log message).
>
> However, the change tricks the following sequence to include a
> merge message in a completely unrelated commit:
>
> $ git pull somewhere
> : oops, the conflicts are too much. forget it.
> $ git reset --hard
> : work work work
> $ git commit
>
> To fix this confusion, this patch makes "git reset" to remove
> the leftover MERGE_MSG that was prepared when the user abandoned
> the merge.
>
> Signed-off-by: Junio C Hamano <junkio@cox.net>
Acked-by: Luben Tuikov <ltuikov@yahoo.com
>
> ---
>
> * 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 also cannot think of any offhand. Should be safe to commit.
Luben
>
> git-reset.sh | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/git-reset.sh b/git-reset.sh
> index 3133b5b..c0feb44 100755
> --- a/git-reset.sh
> +++ b/git-reset.sh
> @@ -63,6 +63,7 @@ case "$reset_type" in
> ;;
> esac
>
> -rm -f "$GIT_DIR/MERGE_HEAD" "$GIT_DIR/rr-cache/MERGE_RR" "$GIT_DIR/SQUASH_MSG"
> +rm -f "$GIT_DIR/MERGE_HEAD" "$GIT_DIR/rr-cache/MERGE_RR" \
> + "$GIT_DIR/SQUASH_MSG" "$GIT_DIR/MERGE_MSG"
>
> exit $update_ref_status
>
>
>
next prev parent reply other threads:[~2006-12-05 6:19 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 [this message]
2006-12-05 8:22 ` Johannes Schindelin
2006-12-05 8:36 ` Andreas Ericsson
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=953031.74197.qm@web31806.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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.