From: Daniel Drake <dsd@gentoo.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [git] libata-dev queue updated
Date: Fri, 19 Aug 2005 10:55:51 +0100 [thread overview]
Message-ID: <4305ACA7.6010101@gentoo.org> (raw)
In-Reply-To: <20050819035437.GA18324@havoc.gtf.org>
Hi Jeff,
Jeff Garzik wrote:
> I finally got around to creating something that has been missing since
> BitKeeper disappeared, and something that Andrew has been wanting
> from me for a while: an amalgamation of all the libata-dev branches
> that I maintain internally.
You are missing two sata_promise ID additions which were sent 2-3 weeks ago.
Should I resend?
Thanks,
Daniel
next prev parent reply other threads:[~2005-08-19 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 3:54 [git] libata-dev queue updated Jeff Garzik
2005-08-19 9:55 ` Daniel Drake [this message]
2005-08-22 4:40 ` Jeff Garzik
2005-08-19 11:42 ` Brett Russ
2005-08-19 17:45 ` 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=4305ACA7.6010101@gentoo.org \
--to=dsd@gentoo.org \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).