mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Len Brown <lenb@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] ACPI patches for 2.6.23
Date: Sun, 22 Jul 2007 11:13:08 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0707221104420.3607@woody.linux-foundation.org> (raw)
In-Reply-To: <200707220535.05527.lenb@kernel.org>



On Sun, 22 Jul 2007, Len Brown wrote:
> 
> please pull from: 
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git release

Pulled.

Btw, on a mostly unrelated note (and to balance the fact that mostly I 
only speak up to complain), I'd like to say how much I appreciate that not 
only are your git tree histories now clean and readable and don't have 
unnecessary merges, but the use of clear "topic branches" really makes it 
very pleasant to read and see what changed.

I'm certainly hoping the topic branches make your life easier too (ie able 
to track things by topic rather than having changes mixed up), but even if 
it doesn't, I wanted to say that I appreciate how it makes it easier for 
outsiders to follow the "big outline" of your development tree.

So I just wanted to say that I appreciate how it's nice to do "gitk 
ORIG_HEAD.." and see the outline of what has been going on in the ACPI 
tree after I have pulled. And I'm hoping it actually helps you guys too, 
but it's appreciated regardless.

See? Sometimes I can say nice things too.

			Linus "not _always_ grouchy" Torvalds

  reply	other threads:[~2007-07-22 18:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22  9:35 Len Brown
2007-07-22 18:13 ` Linus Torvalds [this message]
2007-07-22 19:24   ` Len Brown

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=alpine.LFD.0.999.0707221104420.3607@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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®