git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>,
	Raphael Assenat <raph@8d.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.24-rc6
Date: Thu, 20 Dec 2007 23:50:05 -0500	[thread overview]
Message-ID: <20071221045005.GF8535@fattire.cabal.ca> (raw)
In-Reply-To: <alpine.LFD.0.9999.0712202026040.21557@woody.linux-foundation.org>

On Thu, Dec 20, 2007 at 08:40:54PM -0800, Linus Torvalds wrote:
> That was a rather long-winded explanation of what happened, mainly because 
> it was all very unexpected to me, and I had personally mistakenly thought 
> the git optimization was perfectly valid and actually had to go through 
> the end result to see what was going on.
> 
> Anyway, the diff on kernel.org should be all ok now, and mirrored out too.
> 

Thanks again for being so quick to track this down, applies fine and is
out for building in rawhide now.

cheers, Kyle

  reply	other threads:[~2007-12-21  4:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.0.9999.0712201731010.21557@woody.linux-foundation.org>
     [not found] ` <20071221024805.GB8535@fattire.cabal.ca>
     [not found]   ` <20071221030152.GC8535@fattire.cabal.ca>
2007-12-21  3:49     ` Linux 2.6.24-rc6 Linus Torvalds
2007-12-21  3:50       ` Kyle McMartin
2007-12-21  4:22       ` Linus Torvalds
2007-12-21  4:40         ` Linus Torvalds
2007-12-21  4:50           ` Kyle McMartin [this message]
2007-12-21  4:58         ` Linus Torvalds
2007-12-21  5:21           ` Linus Torvalds
2007-12-21 17:45             ` Linus Torvalds
2007-12-21 16:56           ` Junio C Hamano

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=20071221045005.GF8535@fattire.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=akpm@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raph@8d.com \
    --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;
as well as URLs for NNTP newsgroup(s).