From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Experimental git repositories available for SATA
Date: Thu, 12 May 2005 16:56:24 -0400 [thread overview]
Message-ID: <4283C2F8.6020801@pobox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
I have finally gotten around to getting 2.6.x libata development moved
over from BitKeeper to git.
The "for Linus/Andrew" repository is libata-2.6.git, available at
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-2.6.git/
The new libata-dev repository is libata-dev.git, available at
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git/
A word about these repositories. I don't use any SCM besides git
itself. libata-2.6.git appears as you would expect: .git/HEAD points
to refs/heads/master, which is the top-of-tree, and contains patches
destined for upstream ASAP.
libata-dev.git is a bit different, as it contains multiple branches:
> [jgarzik@pretzel libata-dev]$ ls .git/refs/heads/
> adma atapi-enable iomap pdc2027x
> adma-mwi bridge-detect iomap-step1 pdc20619
> ahci-atapi chs-support master promise-sata-pata
> ahci-msi ioctl-get-identity passthru sil24
I use the attached 'git-switch-tree' script to update the working
directory to reflect the desired branch.
As soon as I am comfortable with git merging, I will create an 'ALL'
branch, which contains all of these trees, merged together properly.
Jeff
[-- Attachment #2: git-switch-tree --]
[-- Type: text/plain, Size: 237 bytes --]
#!/bin/sh
if [ "x$1" != "x" ]
then
if [ ! -f .git/refs/heads/$1 ]
then
echo Branch $1 not found.
exit 1
fi
( cd .git && rm -f HEAD && ln -s refs/heads/$1 HEAD )
fi
git-read-tree $(cat .git/HEAD) && git-checkout-cache -q -f -a
next reply other threads:[~2005-05-12 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 20:56 Jeff Garzik [this message]
2005-05-12 23:01 ` Experimental git repositories available for SATA 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=4283C2F8.6020801@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--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).