From: "Joachim Schmitz" <jojo@schmitz-digital.de>
To: "'Felipe Contreras'" <felipe.contreras@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: [PATCH 1/2] sequencer: trivial fix
Date: Wed, 29 May 2013 13:29:50 +0200 [thread overview]
Message-ID: <001c01ce5c5f$d581b8a0$808529e0$@schmitz-digital.de> (raw)
In-Reply-To: <CAMP44s0U65oxCVy3EwQxF+4ZgRc31z29mwwdO=4x--oFVTFW+g@mail.gmail.com>
> From: Felipe Contreras [mailto:felipe.contreras@gmail.com]
> Sent: Wednesday, May 29, 2013 1:24 PM
> To: Joachim Schmitz
> Cc: git@vger.kernel.org
> Subject: Re: [PATCH 1/2] sequencer: trivial fix
>
> On Wed, May 29, 2013 at 6:13 AM, Joachim Schmitz
> <jojo@schmitz-digital.de> wrote:
> >> From: Felipe Contreras [mailto:felipe.contreras@gmail.com]
> >> Sent: Wednesday, May 29, 2013 12:52 PM
> >> To: Joachim Schmitz
> >> Cc: git@vger.kernel.org
> >> Subject: Re: [PATCH 1/2] sequencer: trivial fix
> >>
> >> On Wed, May 29, 2013 at 4:58 AM, Joachim Schmitz
> >> <jojo@schmitz-digital.de> wrote:
> >> > Felipe Contreras wrote:
> >> >>
> >> >> Junio C Hamano wrote:
> >>
> >> >>> It probably is better to fold this patch into the other one when it
> >> >>> is rerolled to correct the option name gotcha "on the tin".
> >> >>
> >> >>
> >> >> Why? This patch is standalone and fixes an issue that is independent
> >> >> of the other patch. Why squash two patches that do *two* different
> >> >> things?
> >> >>
> >> >> Anyway, I'll happily drop this patch if you want this memory leak to
> >> >> remain. But then I'll do the same in the other patch.
> >> >>
> >> >> This mantra of avodiing 'goto' is not helping anybody.
> >> >
> >> >
> >> > adding 5 letters (to change the next "if" into an "else if") versus your
> >> > addition of several lines and some 15 additional letters (ignoring the
> >> > whitsspace) is IMHO enough to see what is better?
> >>
> >> This has nothing to do with what Junio said.
> >
> > Well, it has, but you had snipped it. But replied to the goto issue regardless
>
> I didn't snip anything, this is a different context.
You did in your reply to me
> >> This is better done without "goto" in general.
>
> He din't say:
> __
> It probably is better to fold this patch into the other one when it
> is rerolled to correct the option name gotcha "on the tin", AND you
> fix the goto issue.
> __
>
> You added that last part in your mind. Moreover, he didn't say goto
> was an issue, he simply stated an opinion about some generality.
I added nothing in my mind, I just copy/paste that statement and was commenting on that and only that.
At least intended to.
Whenever anybody added more else branches, that's the time to possible switch to the goto style.
And for the record: I agree with you that these 2 things should rather not be in a single patch as they are completely unrelated.
Bye, Jojo
next prev parent reply other threads:[~2013-05-29 11:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 16:52 [PATCH 0/2] cherry-pick: a fix and a new option Felipe Contreras
2013-05-27 16:52 ` [PATCH 1/2] sequencer: trivial fix Felipe Contreras
2013-05-28 11:00 ` Neil Horman
2013-05-28 17:04 ` Junio C Hamano
2013-05-29 2:32 ` Felipe Contreras
2013-05-29 9:58 ` Joachim Schmitz
2013-05-29 10:51 ` Felipe Contreras
2013-05-29 11:13 ` Joachim Schmitz
2013-05-29 11:23 ` Felipe Contreras
2013-05-29 11:29 ` Joachim Schmitz [this message]
2013-05-29 11:37 ` Joachim Schmitz
2013-05-29 13:13 ` Neil Horman
2013-05-29 13:25 ` Duy Nguyen
2013-05-29 13:34 ` Felipe Contreras
2013-05-29 13:42 ` Duy Nguyen
2013-05-29 13:46 ` Felipe Contreras
2013-05-29 13:54 ` Duy Nguyen
2013-05-29 14:10 ` Felipe Contreras
2013-05-27 16:52 ` [PATCH 2/2] cherry-pick: add --skip-commits option Felipe Contreras
2013-05-28 10:29 ` Joachim Schmitz
2013-05-28 11:06 ` Neil Horman
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='001c01ce5c5f$d581b8a0$808529e0$@schmitz-digital.de' \
--to=jojo@schmitz-digital.de \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).