From: Brandon Casey <drafnel@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-branch: display "was sha1" on branch deletion rather than just "sha1"
Date: Sun, 22 Mar 2009 10:11:43 -0500 [thread overview]
Message-ID: <ee63ef30903220811m69c45e9cna0af52a3b5a851fe@mail.gmail.com> (raw)
In-Reply-To: <20090322061320.GB14765@coredump.intra.peff.net>
On Sun, Mar 22, 2009 at 1:13 AM, Jeff King <peff@peff.net> wrote:
> On Sat, Mar 21, 2009 at 07:09:17PM -0500, Brandon Casey wrote:
>
>> Make it more pleasant to read about a branch deletion by adding "was".
>> Jeff King suggested this, and I ignored it. He was right.
>
> Heh. While I am tempted to dance in a circle shouting "I told you so", I
> actually find that after getting used to it, I do not mind the current
> output. ;)
>
> Out of curiosity, what prompted your change of heart? Did you hear from
> somebody who found it confusing, or did you just change your mind?
I just changed my mind.
My original opinion was based on the output from 'git stash drop'. It
has the full sha1 in the message and looks like:
$git stash drop
Dropped refs/stash@{0} (58fa28fddd951deb782e3300b2d059f95544f6f1)
I like it. I like the full sha1.
For some reason, the partial sha1 in the branch delete message irritated me.
$ git branch -d mybranch
Deleted branch mybranch (455f59b).
I don't think it was because it was a partial sha1. Maybe it was
because the message seemed to imply that what was referenced by the
sha1 was being deleted. The branch is just a pointer, so deleting it
does not mean that what it pointed at was lost in any way. I think
adding "was" makes it seem more like a pointer to me. Or maybe it has
something to do with my mother, any psychology majors in the audience?
:)
-brandon
prev parent reply other threads:[~2009-03-22 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 0:09 [PATCH] git-branch: display "was sha1" on branch deletion rather than just "sha1" Brandon Casey
2009-03-22 6:13 ` Jeff King
2009-03-22 15:11 ` Brandon Casey [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=ee63ef30903220811m69c45e9cna0af52a3b5a851fe@mail.gmail.com \
--to=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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 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).