linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: torvalds@osdl.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [git patches] 2.6.x libata update
Date: Sun, 30 Oct 2005 12:39:07 -0800	[thread overview]
Message-ID: <20051030123907.6ea5d442.akpm@digeo.com> (raw)
In-Reply-To: <20051030194512.GA21782@havoc.gtf.org>

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.

  reply	other threads:[~2005-10-30 20:39 UTC|newest]

Thread overview: 4+ 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 [this message]
2005-10-30 21:45   ` Linus Torvalds
  -- 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=20051030123907.6ea5d442.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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).