All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
	mingo@elte.hu, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, geert@linux-m68k.org
Subject: Re: [PATCH] v3 kconfig: place git SHA1 in .config output if in SCM
Date: Fri, 5 Mar 2010 12:49:41 -0800	[thread overview]
Message-ID: <20100305204941.GI6764@linux.vnet.ibm.com> (raw)
In-Reply-To: <201003052131.12199.elendil@planet.nl>

On Fri, Mar 05, 2010 at 09:31:10PM +0100, Frans Pop wrote:
> (Dropping cloos as that address is bouncing my mails.)
> 
> On Friday 05 March 2010, Paul E. McKenney wrote:
> > s/you're over-designing this/you are freaking paranoid/
> 
> Whatever makes you happy :-)

;-)

> > With that change, I plead guilty to charges as read.  But again, I am
> > worried about the case where one person generates the .config file
> > and someone else is reading it.
> 
> Not sure that's very relevant. A person reading it will still get the same 
> oldfashioned basic info as when a build is done from a tree that's not 
> under an SCM. And he won't really be in a position where he can fix the 
> errors anyway.

But the person reading it is in a position to ask the person sending the
.config to fix their build system.

							Thanx, Paul

  reply	other threads:[~2010-03-05 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05  2:54 [PATCH] v3 kconfig: place git SHA1 in .config output if in SCM Paul E. McKenney
2010-03-05  3:43 ` Frans Pop
2010-03-05  5:20   ` Paul E. McKenney
2010-03-05 17:18     ` Frans Pop
2010-03-05 20:10       ` Paul E. McKenney
2010-03-05 20:31         ` Frans Pop
2010-03-05 20:49           ` Paul E. McKenney [this message]
2010-03-05  6:10 ` Mike Galbraith
2010-03-05 12:57   ` Paul E. McKenney

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=20100305204941.GI6764@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=elendil@planet.nl \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.