From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Micheil Smith <micheil@brandedcode.com>, git@vger.kernel.org
Subject: Re: Proposal for git stash rename
Date: Wed, 09 Jan 2013 09:38:16 +0100 [thread overview]
Message-ID: <50ED2C78.1030300@alum.mit.edu> (raw)
In-Reply-To: <7vbod4tynt.fsf@alter.siamese.dyndns.org>
On 01/04/2013 10:40 PM, Junio C Hamano wrote:
> Micheil Smith <micheil@brandedcode.com> writes:
>
>>> This patch implements a "git stash rename" using a new
>>> "git reflog update" command that updates the message associated
>>> with a reflog entry.
>> ...
>> I note that this proposal is now two years old. A work in progress patch was
>> requested, however, after one was given this thread ended. I'm also finding
>> a need for this feature;
>
> The whole point of reflog is that it is a mechanism to let users to
> go safely back to the previous state, by using a file that is pretty
> much append-only. It feels that a mechanism to "rewrite" one goes
> completely against that principle, at least to me.
The implementation of "git stash" itself seems to violate your
principle, by storing its branches-that-are-not-branches within a
mutable reflog.
Just an observation...
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
prev parent reply other threads:[~2013-01-09 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 9:31 Proposal for git stash rename Greg Hewgill
2010-06-20 10:54 ` Ævar Arnfjörð Bjarmason
2010-06-20 11:11 ` Greg Hewgill
2013-01-04 18:25 ` Micheil Smith
2013-01-04 21:40 ` Junio C Hamano
2013-01-09 8:38 ` Michael Haggerty [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=50ED2C78.1030300@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=micheil@brandedcode.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).