From: Nick Piggin <npiggin@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Nick Piggin <npiggin@kernel.dk>
Subject: Re: [PATCH,TRIVIAL] Replace Configure with Enable in description of MAXSMP
Date: Tue, 24 Aug 2010 17:43:39 +1000 [thread overview]
Message-ID: <20100824074339.GG3948@amd> (raw)
In-Reply-To: <AANLkTi=Pha8jRFhr+kQfh9doKZDW-=VHq2KqNxXaq6ts@mail.gmail.com>
On Sat, Aug 21, 2010 at 12:45:12PM -0700, Linus Torvalds wrote:
> On Sat, Aug 21, 2010 at 12:32 PM, Samuel Thibault
> <samuel.thibault@ens-lyon.org> wrote:
> >
> > Replace Configure with Enable in description of MAXSMP
> >
> > The "Configure" word tends to make user believe they have to say 'yes'
> > to be able to choose the number of procs/nodes. "Enable" should be
> > unambiguous enough.
>
> What broken patch-generation tools do you use, btw? Nick Piggin has
> the same problem: the Subject of the patch gets repeated as the first
> line of the body of the thing, which is very annoying. Either I have
> to go in and edit the email (which I try to do), or the thing gets
> repeated in the commit message.
I'm sorry about that :( I did try applying it here locally which seemed
to work, but something obviously went wrong between then and sending it.
prev parent reply other threads:[~2010-08-24 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 19:32 [PATCH,TRIVIAL] Replace Configure with Enable in description of MAXSMP Samuel Thibault
2010-08-21 19:45 ` Linus Torvalds
2010-08-21 19:55 ` Samuel Thibault
2010-08-21 20:05 ` Sam Ravnborg
2010-08-21 20:10 ` Samuel Thibault
2010-08-21 20:16 ` Linus Torvalds
2010-08-21 20:27 ` Linus Torvalds
2010-08-24 7:43 ` Nick Piggin [this message]
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=20100824074339.GG3948@amd \
--to=npiggin@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=torvalds@linux-foundation.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