From: "Lars Hjemli" <hjemli@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Miklos Vajna" <vmiklos@frugalware.org>,
git@vger.kernel.org
Subject: Re: [PATCH 3/3] builtin-branch: use strbuf in rename_branch()
Date: Wed, 19 Nov 2008 20:48:48 +0100 [thread overview]
Message-ID: <8c5c35580811191148m45cdff68vbe190ef911066da8@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0811190209470.30769@pacific.mpi-cbg.de>
On Wed, Nov 19, 2008 at 02:11, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 18 Nov 2008, Junio C Hamano wrote:
>
>> Miklos Vajna <vmiklos@frugalware.org> writes:
>>
>> > - snprintf(logmsg, sizeof(logmsg), "Branch: renamed %s to %s",
>> > - oldref, newref);
>> > + strbuf_addf(&logmsg, "Branch: renamed %s to %s",
>> > + oldref.buf, newref.buf);
>>
>> I am wondering why nobody has complained until now, but shouldn't this
>> be oldname and newname?
>
> I think that was the intention. Lars?
Some background: the message was first generated internally (in
c976d415) by refs.c:rename_ref() and thus it made sense to use the
full refname. Sometime later (in 678d0f4c), rename_ref() was modified
to get the message as an argument from
builtin_branch.c:rename_branch() but the format of the message was
kept (almost) identical.
Personally, I think it's nice if the reflog contains the full refname.
--
larsh
prev parent reply other threads:[~2008-11-19 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 20:48 [PATCH 0/3] builtin-branch: use strbuf Miklos Vajna
2008-11-17 20:48 ` [PATCH 1/3] builtin-branch: use strbuf in delete_branches() Miklos Vajna
2008-11-17 20:48 ` [PATCH 2/3] builtin-branch: use strbuf in fill_tracking_info() Miklos Vajna
2008-11-17 20:48 ` [PATCH 3/3] builtin-branch: use strbuf in rename_branch() Miklos Vajna
2008-11-18 23:57 ` Junio C Hamano
2008-11-19 1:11 ` Johannes Schindelin
2008-11-19 19:48 ` Lars Hjemli [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=8c5c35580811191148m45cdff68vbe190ef911066da8@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vmiklos@frugalware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox