From: Clemens Buchacher <drizzd@aon.at>
To: "Nathan W. Panike" <nathan.panike@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Looking for a way to turn off/modify ref disambiguation
Date: Wed, 24 Aug 2011 08:54:12 +0200 [thread overview]
Message-ID: <20110824065412.GA10800@ecki> (raw)
In-Reply-To: <CAPRoxBXjL3Y3KRd8R2guX9Ar374sw-pBhz1bCzNZxn1vC6XNPw@mail.gmail.com>
Hi Nathan,
On Tue, Aug 23, 2011 at 02:26:48PM -0500, Nathan W. Panike wrote:
>
> Is there any way to change this behavior, e.g., so that rule 6 becomes
> an error? Say, by setting a config option?
I know you're trying to improve git. I do not want to discourage
that. But with little UI annoyances like this, it's usually not
worth it. Git has countless magic tricks like this. It's a bit
like perl in that regard. Assuming that we agree on what we would
like to get rid of (which is the hard part), it would still break
backwards compatibility. Maintaining a switch, on the other hand,
is overhead and in the end it would make git even more complicated,
because now the behavior of core commands depends on user
configuration.
But once you accept the fact that this is what git is, you can
tackle the problem in a different way:
> A colleague at $dayjob recently caused corruption in our git
> repository by accidentally running the command
>
> git rebase origin stable
Ok, mistakes happen. But that's exactly why you have git: To be
able to deal with mistakes gracefully. So use git to review and
test changes before they get declared as a stable release (stable
enough to be used internally, at least). Then mistakes usually
become a local problem and can be undone using the reflog.
Clemens
prev parent reply other threads:[~2011-08-24 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 19:26 Looking for a way to turn off/modify ref disambiguation Nathan W. Panike
2011-08-23 21:15 ` Jeff King
2011-08-23 22:03 ` Junio C Hamano
2011-08-24 9:25 ` Michael J Gruber
2011-08-24 16:37 ` Jonathan Nieder
2011-08-24 17:48 ` Junio C Hamano
2011-08-24 6:54 ` Clemens Buchacher [this message]
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=20110824065412.GA10800@ecki \
--to=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=nathan.panike@gmail.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).