git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Оля Тележная" <olyatelezhnaya@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] ref-filter: get rid of goto
Date: Thu, 22 Feb 2018 08:35:04 +0300	[thread overview]
Message-ID: <CAL21Bm=FptUV3xRnYf-iiht8HQF+-uF=cOZyybh7VNCmP=Nxbg@mail.gmail.com> (raw)
In-Reply-To: <xmqqpo4yz1cw.fsf@gitster-ct.c.googlers.com>

2018-02-21 20:41 GMT+03:00 Junio C Hamano <gitster@pobox.com>:
> Olga Telezhnaya <olyatelezhnaya@gmail.com> writes:
>
>> Get rid of goto command in ref-filter for better readability.
>>
>> Signed-off-by: Olga Telezhnaia <olyatelezhnaya@gmail.com>
>> Mentored-by: Christian Couder <christian.couder@gmail.com>
>> Mentored by: Jeff King <peff@peff.net>
>> ---
>>  ref-filter.c | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> It looks like this is the same change as the bottom-most change on
> your "cat-file --batch" series (and is obviously correct).
>
> I am puzzled by your intention---are you re-organizing and rebooting
> the series?  Either 'Yes' or 'No' is an acceptable answer, and so is
> anything else.  I just want to know what you want to happen to the
> merge conflicts if I queued this while still keeping your "cat-file
> --batch" thing I have on 'pu').

Thanks for the question, I needed to mention that.
We (with Peff) decided that it's better and easier to remake whole
previous patch. Before that, I want to make some refactorings in
ref-filter so after that migrating should go much easier. I want to do
that by small separate patches, so this is first in the series. I hope
it would be both easier to review for you and easier to fix for me.
So, if everything is fine, you could merge it to master. I will
rewrite most parts of previous patch anyway.

Thanks!

>
>>
>> diff --git a/ref-filter.c b/ref-filter.c
>> index 83ffd84affe52..28df6e21fb996 100644
>> --- a/ref-filter.c
>> +++ b/ref-filter.c
>> @@ -1494,11 +1494,11 @@ static void populate_value(struct ref_array_item *ref)
>>       for (i = 0; i < used_atom_cnt; i++) {
>>               struct atom_value *v = &ref->value[i];
>>               if (v->s == NULL)
>> -                     goto need_obj;
>> +                     break;
>>       }
>> -     return;
>> +     if (used_atom_cnt <= i)
>> +             return;
>>
>> - need_obj:
>>       get_object(ref, &ref->objectname, 0, &obj);
>>
>>       /*
>>
>> --
>> https://github.com/git/git/pull/460

  reply	other threads:[~2018-02-22  5:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21  6:59 [PATCH 1/2] ref-filter: get rid of duplicate code Olga Telezhnaya
2018-02-21  6:59 ` [PATCH 2/2] ref-filter: get rid of goto Olga Telezhnaya
2018-02-21 17:41   ` Junio C Hamano
2018-02-22  5:35     ` Оля Тележная [this message]
2018-02-21  7:02 ` [PATCH v2 1/2] ref-filter: get rid of duplicate code Olga Telezhnaya
2018-02-21  7:02   ` [PATCH v2 2/2] ref-filter: get rid of goto Olga Telezhnaya
2018-02-21 17:33 ` [PATCH 1/2] ref-filter: get rid of duplicate code 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='CAL21Bm=FptUV3xRnYf-iiht8HQF+-uF=cOZyybh7VNCmP=Nxbg@mail.gmail.com' \
    --to=olyatelezhnaya@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).