From: Junio C Hamano <gitster@pobox.com>
To: Tim Chase <git@tim.thechases.com>
Cc: git@vger.kernel.org
Subject: Re: Archiving off old branches
Date: Wed, 23 Apr 2014 10:43:07 -0700 [thread overview]
Message-ID: <xmqqzjjcymac.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140423120850.3f6fb535@bigbox.christie.dr> (Tim Chase's message of "Wed, 23 Apr 2014 12:08:50 -0500")
Tim Chase <git@tim.thechases.com> writes:
> Reading up on "git help update-ref", it states that it updates the
> name "safely".
I think that description is well intended but is misleading. There
are many potential sources of risk, and the "safely" refers to
protection against a particular kind of risk: updating from a value
that you did not intend to (i.e. you examined and decided the update
is good, time passes while somebody else might have mucked with the
ref, and then you execute the update you decided to do). And the
safety afforded to you is with "git update-ref ref newvalue oldvalue"
that makes sure the ref still points at the oldvalue and refuses to
update it to newvalue if it doesn't.
next prev parent reply other threads:[~2014-04-23 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 17:08 Archiving off old branches Tim Chase
2014-04-23 17:43 ` Junio C Hamano [this message]
2014-04-23 17:58 ` Jonathan Nieder
2014-04-23 18:06 ` Tim Chase
2014-04-23 18:15 ` 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=xmqqzjjcymac.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@tim.thechases.com \
--cc=git@vger.kernel.org \
/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.