public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [git patches] 2.6.x libata update
Date: Sun, 30 Oct 2005 22:02:28 -0600	[thread overview]
Message-ID: <200510302202.28690.rob@landley.net> (raw)
In-Reply-To: <20051030123907.6ea5d442.akpm@digeo.com>

On Sunday 30 October 2005 14:39, Andrew Morton wrote:
> Jeff Garzik <jgarzik@pobox.com> wrote:
> > Please pull from 'upstream-linus' branch of
> >  master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>
> Linus may not receive this.  For me at least, large amounts of incoming and
> outgoing OSDL email have been disappearing into the ether for the past 12
> hours or so.

It's probably delayed.  I got the "could not deliver for 4 hours, connection 
with smtp.osdl.org timed out" warning on the original "Is this a viable 
option?" question, and Linus has since replied, so it went through...

Rob

P.S.  The git source also wanted the -dev version of libcurl installed, 
whatever that is.  Been happily banging on this box for months without ever 
needing it.  Am now reading through the git tutorial.  Very dry.

I read through the git bisect source (well, the bits in rev-list.c anyway), 
and yeah it's cheating mightily with the "distance" thing, and by supplying 
"good" and "bad" you're actually making the greater than or less than 
decisions yourself.  Whee.

If all else fails, it's got a sort-by-date function in there, so if you plug 
the date thing in for the good and bad you at least get something consistent, 
but I can see Linus's warnings about huge, evil, unintelligible revisions 
from jumping around like that.

Of course you don't have to make the ordering decision right away: I get two 
halves, and can bisect each one all the way to binary tree without having to 
make a single greater than or less than decision.  Then when putting the tree 
back together, the criteria is "which direction produces the smallest 
cumulative patch", which isn't nicely resolving in my head into code yet but 
I'm working on it...

Need to get a kernel tree to play with, which means finishing this tutorial.

Need... more... caffeine.

Still Rob

  parent reply	other threads:[~2005-10-31  4:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-30 19:45 [git patches] 2.6.x libata update Jeff Garzik
2005-10-30 20:39 ` Andrew Morton
2005-10-30 21:45   ` Linus Torvalds
2005-10-31  4:02   ` Rob Landley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-18 18:17 Jeff Garzik

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=200510302202.28690.rob@landley.net \
    --to=rob@landley.net \
    --cc=akpm@digeo.com \
    --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