From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-merge -s theirs
Date: Sun, 20 Jul 2008 14:22:28 -0700 [thread overview]
Message-ID: <7vhcak45ez.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080720192130.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Sun, 20 Jul 2008 19:21:30 +0900")
Nanako Shiraishi <nanako3@lavabit.com> writes:
> This patch steals much code from "git-merge-resolve" to add "theirs"
> strategy. Its purpose is to always fail and suggest using the preferred
> command "git reset --hard the-other-commit".
> ...
> +echo "If you wanted to say the other history is better than your history,"
> +echo "use 'git reset --hard $remotes' instead."
> +echo "If you want to keep a record of your failure, you can create a"
> +echo "new branch from the current HEAD before running the reset command."
> +
> +exit 2
That is certainly cute, but I do not like it for two reasons:
- This advertizes "theirs" as available when you ask "git merge -s whoa",
and then the user is told "don't use this stupid, go away". That is
not exactly a good diplomacy to earn friends.
- The message gives a rather long hexdecimal string in its suggestion to
run "git reset --hard". This is not exactly your fault, though. The
original refname the user gave to "git-merge" is not available to your
strategy.
next prev parent reply other threads:[~2008-07-20 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 10:21 [PATCH] git-merge -s theirs Nanako Shiraishi
2008-07-20 21:22 ` Junio C Hamano [this message]
2008-07-28 9:18 ` Re* " Junio C Hamano
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=7vhcak45ez.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).