From: Bert Wesarg <bert.wesarg@googlemail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jay Soffian <jaysoffian@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] get_ref_states: strdup entries and free util in stale list
Date: Tue, 1 Dec 2009 10:32:37 +0100 [thread overview]
Message-ID: <36ca99e90912010132iee0d42fo933aeb12833ad1ad@mail.gmail.com> (raw)
In-Reply-To: <7vy6ln2llw.fsf@alter.siamese.dyndns.org>
On Tue, Dec 1, 2009 at 08:34, Junio C Hamano <gitster@pobox.com> wrote:
> Bert Wesarg <bert.wesarg@googlemail.com> writes:
>
>> On Tue, Dec 1, 2009 at 01:21, Junio C Hamano <gitster@pobox.com> wrote:
>> ...
>>> Hmm, the Subject: matches what the code does, but nobody mentions why it
>>> is necessary (iow, what breaks in the current code and what becomes better
>>> if the patch is applied). The blank space before your "S-o-b:" line is
>>> for you to describe these things.
>> Sure. unfortunately the code where the string list is filled is not in
>> the patch. But if you look at the code it should be self-explanatory.
>
> That is _exactly_ why I want the description in the commit log message. I
> don't want commit messages (or lack thereof) to force people to look at
> the code outside the patch.
>
> Otherwise I'll have to ask _you_ to personally give the 7-line explanation
> you just gave us to anybody who runs "git log -p" with the default context
> size after this patch is applied. I do not think you have the bandwidth
> to handle that ;-).
Yes. That makes perfectly sense. Sorry for the hassle.
>
>> There is actually also an other solution: we could first strdup the
>> ref name to the .util member and take this as the input for the
>> abbrev_ref()/string list entry and safe there the strdup.
>
> I too thought something like that may make sense, but it doesn't look like
> so, for two reasons:
>
> - string-list API is a bit cumbersome to use if you allocate the string
> yourself. You will be made responsible for freeing them, and often you
> do so by setting strdup_strings to true immediately before calling
> string_list_clear(), which is kind of ugly;
>
> - The ref abbrev_branch() is called and the address of whose substring is
> taken to be used as "name" in handle_one_branch() is refspec.src, but
> what goes to .util is refname that is refspec.dst---they are different
> strings and one is not a substring of the other.
I don't see you point here. The current code is:
for (ref = stale_refs; ref; ref = ref->next) {
struct string_list_item *item =
string_list_append(abbrev_branch(ref->name), &states->stale);
item->util = xstrdup(ref->name);
}
So 0 == strcmp(item->string, abbrev_ref(item->util, "refs/heads/"))
should be true, shouldn't it?
Bert
next prev parent reply other threads:[~2009-12-01 9:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 23:57 [PATCH] get_ref_states: strdup entries and free util in stale list Bert Wesarg
2009-12-01 0:21 ` Junio C Hamano
2009-12-01 6:49 ` Bert Wesarg
2009-12-01 7:34 ` Junio C Hamano
2009-12-01 9:32 ` Bert Wesarg [this message]
2009-12-01 17:20 ` Junio C Hamano
2009-12-01 18:14 ` Bert Wesarg
2009-12-01 19:20 ` Junio C Hamano
2009-12-01 8:35 ` Johannes Schindelin
2009-12-01 9:05 ` Bert Wesarg
2009-12-01 15:53 ` Bert Wesarg
2009-12-01 18:20 ` Bert Wesarg
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=36ca99e90912010132iee0d42fo933aeb12833ad1ad@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@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).