From: Tony Luck <tony.luck@intel.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
cl@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [GIT PULL] SLAB changes for v2.6.38
Date: Tue, 11 Jan 2011 13:25:17 -0800 [thread overview]
Message-ID: <AANLkTim29V8-w23zc=akW+F3CW-BKYR=jpWRVnr3x4E0@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiknwXJF+pLJFQPqa7XPywi=boz-H+_JLk-T+Zp8@mail.gmail.com>
On Tue, Jan 11, 2011 at 8:13 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> That said, "number of commits" is not a really meaningful measure
> either. I really tend to like how the ACPI tree does things, with
> separate branches for separate bugzilla entries - with nice relevant
> branch naming (bug number or description) - and then merging them. At
> that point you may well have a branch with just a single commit in it,
> but now the extra merge actually _adds_ information and the history
> looks better for it.
There are some notes on this work flow in the git sources in
Documentation/user-manual.txt in the [[maintaining-topic-branches]]
chapter.
-Tony
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-01-11 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 9:13 Pekka Enberg
2011-01-10 16:44 ` Linus Torvalds
2011-01-11 10:41 ` Pekka Enberg
2011-01-11 16:13 ` Linus Torvalds
2011-01-11 21:25 ` Tony Luck [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='AANLkTim29V8-w23zc=akW+F3CW-BKYR=jpWRVnr3x4E0@mail.gmail.com' \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.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