public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Dirk Gouders <dirk@gouders.net>,
	Jan Beulich <JBeulich@novell.com>, Michal Marek <mmarek@suse.cz>,
	linux-kbuild@vger.kernel.org
Subject: Re: kconfig/menu.c: Fixup to "kconfig: fix undesirable side effect of adding "visible" menu attribute" ?
Date: Wed, 31 Jul 2013 18:53:40 +0200	[thread overview]
Message-ID: <20130731165340.GA3448@free.fr> (raw)
In-Reply-To: <CA+icZUXL3trj_Zfisxek8dw4HtNbx2fNDq=Gwn5zKjbNh8GDMg@mail.gmail.com>

Sedat, Dirk, All,

On 2013-07-31 16:22 +0200, Sedat Dilek spake thusly:
> On Wed, Jul 31, 2013 at 4:16 PM, Dirk Gouders <dirk@gouders.net> wrote:
> > Sedat Dilek <sedat.dilek@gmail.com> writes:
> >> The Freetz router project has 370 [1] as a revert-patch of [2] to its
> >> kconfig-v3.8.
> >>
> >> commit 7ad1227818f09242cfe9bf1845fd24211f5f99bd
> >> "kconfig: fix undesirable side effect of adding "visible" menu attribute"
> >>
> >> I am not a kconfig-expert, but [3] looks like a fixup/folowup to it.
> >>
> >> commit/?id=e983b7b17ad1a978e954e6aaa62cf12bfc747883
> >> "kconfig/menu.c: fix multiple references to expressions in menu_add_prop()"
> >>
> >> I contacted Yann in private, but I think this is worth to ask on the
> >> linux-kbuild ML.

Yes, there was no reason to write such a question in private.

> > you are right, [3] fixes a problem that was introduced by [2].
> > (I should have noted that in the commit message -- I'm not sure if we
> > can fix that afterwards.)

No, it's been pushed to a public tree, it's too late.
It's even in Linus' tree, so it is really too late!

> thanks for the clarification and fixing this up.
> I told Yann in my private email to always add a reference to the
> "culprit" commit (root-cause).

Since I was not the author of that patch, I have no way to know if it is
"a fix for a previous commit", or "just a fix", if the original author
does not provide this information.

Except for the patches I write, I "just" collect (and test/review) the
patches to kconfig in my tree, to make it a bit easier for Michal. I
just pass the patches' commit logs as-is (or do trivial edits if
needed), so what gets in the tree is the responsibility of the author.
Hey, Dirk! ;-)

But on the principle, I do agree: if the patch fixes a regression
introduced by a previous changeset, it should be referenced in the
commit log of that new patch, indeed.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-07-31 16:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 17:11 kconfig/menu.c: Fixup to "kconfig: fix undesirable side effect of adding "visible" menu attribute" ? Sedat Dilek
2013-07-31 14:16 ` Dirk Gouders
2013-07-31 14:22   ` Sedat Dilek
2013-07-31 16:53     ` Yann E. MORIN [this message]
2013-07-31 17:12       ` Sedat Dilek
2013-08-01  6:21         ` Dirk Gouders
2013-08-01  6:51           ` Sedat Dilek
2013-08-01  7:01             ` Sedat Dilek
2013-08-01  7:17           ` Sedat Dilek
2013-08-02  6:11             ` Sedat Dilek
2013-08-02  8:59               ` Dirk Gouders
2013-08-02 16:10                 ` Sedat Dilek
2013-08-02 16:48                   ` Yann E. MORIN

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=20130731165340.GA3448@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=JBeulich@novell.com \
    --cc=dirk@gouders.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sedat.dilek@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