From: Hugh Dickins <hugh@veritas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Len Brown <len.brown@intel.com>, Andi Kleen <ak@suse.de>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix maxcpus=N parsing
Date: Mon, 27 Aug 2007 21:53:49 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708272151510.3326@blonde.wat.veritas.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0708271009270.25853@woody.linux-foundation.org>
On Mon, 27 Aug 2007, Linus Torvalds wrote:
> On Mon, 27 Aug 2007, Hugh Dickins wrote:
> >
> > Fix 61ec7567db103d537329b0db9a887db570431ff4: maxcpus=N is now having no
> > ...
>
> On a totally unrelated issue:
>
> While looking at the history in gitk and gitweb etc shows these commit
> ID's as nice hyperlinks, I really think it's nicer for everybody if the
> commit is also described with its "headline", so that non-git users (or
> even git users, when just using "git log" or similar) at least can grep or
> google for it.
>
> So when writing descriptions, I would prefer it if people wrote them
> something like
>
> Commit 61ec7567db103d537329b0db9a887db570431ff4 ('ACPI: boot correctly
> with "nosmp" or "maxcpus=0"') broke maxcpus parsing on x86[-64] ...
>
> so that it gets both the exact commit naming and the nice hyperlinks where
> appropriate *and* it ends up being more useful even without the links.
Agreed and noted.
>
> Yes, it's redundant information, but since we have the useful one-line
> descriptions, it's generally a good idea. And I really do think that it
> tends to make the explanations read better too.
>
> For example, in this example, I think it really made it more clear what
> kind of change had caused the breakage. Maybe that's not always true, but
> I suspect it's true most of the time.
>
> I'll fix it up manually (I often do), but I thought I'd just mention this
> stylistic issue.
Thanks.
Hugh
next prev parent reply other threads:[~2007-08-27 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 15:02 Hugh Dickins
2007-08-27 17:20 ` Linus Torvalds
2007-08-27 20:53 ` Hugh Dickins [this message]
2007-08-28 17:58 ` Rusty Russell
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=Pine.LNX.4.64.0708272151510.3326@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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
all inboxes | Powered by JetHome®