From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <liml@rtr.ca>
Cc: Greg Stark <gsstark@mit.edu>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [SATA] libata-dev queue updated
Date: Wed, 22 Jun 2005 16:23:07 -0400 [thread overview]
Message-ID: <42B9C8AB.8040001@pobox.com> (raw)
In-Reply-To: <42B98EBF.7020500@rtr.ca>
Mark Lord wrote:
> Jeff Garzik wrote:
>
>> Greg Stark wrote:
>>
>>> So, uh, where do I get git? Where is your "git repository" and Linus'
>>> "git repository" and how do I set that up?
>>
>>
>> http://lkml.org/lkml/2005/5/26/11
>>
>> Jeff
>
>
> Okay, so now I have two separate git repositories,
> one for Linus's tree (currently at 2.6.12), and another
> that is Jeff's libata-dev bundle of goodies.
>
> But I have no idea whatsoever what to do next.
>
> What I *want*, is the patchset for "passthru",
> so that I can apply those patches to 2.6.12 and
> then test that kernel.
>
> But it is nowhere even remotely close to possibly perhaps
> someday eventually maybe suggestively obvious how to do that.
Boy that's an unparseable sentence, if I ever saw one :)
You can obtain a patch from the 'passthru' branch by doing
git checkout -f passthru
git-diff-tree -p master HEAD > /tmp/patch
or simply by downloading what I just uploaded a few minutes ago,
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.12-git4-passthru1.patch.bz2
next prev parent reply other threads:[~2005-06-22 20:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 6:08 [SATA] libata-dev queue updated Jeff Garzik
2005-06-04 15:17 ` Greg Stark
2005-06-04 17:48 ` Jeff Garzik
2005-06-04 18:50 ` Adrian Bunk
2005-06-04 19:05 ` Jeff Garzik
2005-06-04 19:15 ` Greg Stark
2005-06-04 19:19 ` Jeff Garzik
2005-06-05 2:25 ` Greg Stark
2005-06-05 2:30 ` Jeff Garzik
2005-06-05 5:30 ` Greg Stark
2005-06-22 16:15 ` Mark Lord
2005-06-22 20:23 ` Jeff Garzik [this message]
2005-06-23 3:39 ` Mark Lord
2005-06-05 2:40 ` Drew Winstel
2005-06-05 2:58 ` Jim Crilly
2005-06-06 16:01 ` Mark Lord
2005-06-07 1:57 ` Greg Stark
2005-06-07 11:20 ` Brad Campbell
2005-06-08 8:33 ` Mark Lord
2005-06-07 13:15 ` Brad Campbell
2005-06-08 8:37 ` Mark Lord
2005-06-07 13:51 ` Greg Stark
2005-06-08 10:30 ` Mark Lord
2005-06-08 8:51 ` Mark Lord
2005-06-07 17:53 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 7:00 Bene Martin
2005-03-10 5:40 Jeff Garzik
2005-03-29 9:12 ` kern.petr
2005-03-08 11:20 Jeff Garzik
2005-03-02 2:40 Jeff Garzik
2005-02-19 8:40 Jeff Garzik
2005-02-19 16:58 ` Andre Tomt
2005-02-19 17:09 ` Jeff Garzik
2005-02-13 20:33 Jeff Garzik
2004-10-30 16:15 Jeff Garzik
2004-10-27 6:52 Jeff Garzik
2004-10-27 6:53 ` Jeff Garzik
2004-10-27 22:53 ` Rob van Nieuwkerk
2004-10-27 23:03 ` Jeff Garzik
2004-10-18 23:52 Jeff Garzik
2004-10-16 0:44 Jeff Garzik
2004-10-15 8:04 Jeff Garzik
2004-10-15 17:15 ` 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=42B9C8AB.8040001@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=gsstark@mit.edu \
--cc=liml@rtr.ca \
--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).