From: Adrian Bunk <bunk@stusta.de>
To: Jeff Garzik <jgarzik@pobox.com>
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: Sat, 4 Jun 2005 20:50:28 +0200 [thread overview]
Message-ID: <20050604185028.GZ4992@stusta.de> (raw)
In-Reply-To: <42A1E96C.6080806@pobox.com>
On Sat, Jun 04, 2005 at 01:48:28PM -0400, Jeff Garzik wrote:
> Greg Stark wrote:
> >Jeff Garzik <jgarzik@pobox.com> writes:
> >
> >
> >>Several updates to the libata-dev.git repository. Some of the branches
> >>have
> >>been folded into a new upstream-2.6.13 branch, which holds several
> >>changes (see
> >>attached). Other branches were updated to the most recent kernel, which
> >>contained doc updates that caused some minor merge conflicts.
> >>
> >>I haven't yet updated 'passthru' and 'chs-support' branches to the latest
> >>kernel.
> >>
> >>Git Repository URL:
> >>rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
> >>
> >>List of branches:
> >>adma chs-support master pdc2027x sleeping-eh
> >>adma-mwi iomap ncq promise-sata-pata upstream-2.6.13
> >>atapi-enable iomap-step1 passthru sil24
> >
> >
> >Are there diffs downloadable for these? In particular I'm looking for
> >passthru. I'm imagining that with passthru SMART works?
>
> You'll need to generate the diffs yourself, I'm afraid.
I haven't tried git, but is there really no way to tell git to do
"For every branch, generate a diff against Linus' tree" ?
This together with making them available at some URL would make life
easier for some people.
> Jeff
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-06-04 18:50 UTC|newest]
Thread overview: 57+ 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 [this message]
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
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 13:09 ` Domenico Andreoli
2005-06-07 17:53 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 7:00 Bene Martin
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
[not found] <3Ds62-5AS-3@gated-at.bofh.it>
2005-03-02 20:34 ` Joerg Sommrey
2005-03-02 22:43 ` Jeff Garzik
2005-03-03 19:32 ` Joerg Sommrey
2005-03-04 4:09 ` Jeff Garzik
2005-03-04 6:37 ` Joerg Sommrey
2005-03-04 7:10 ` Jeff Garzik
2005-03-04 17:49 ` Joerg Sommrey
2005-03-04 18:07 ` Jeff Garzik
2005-03-04 20:33 ` Joerg Sommrey
2005-03-04 20:43 ` Jeff Garzik
2005-03-04 22:06 ` Joerg Sommrey
2005-03-04 22:32 ` Joerg Sommrey
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=20050604185028.GZ4992@stusta.de \
--to=bunk@stusta.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=gsstark@mit.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.