From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev repo has changed to git
Date: Fri, 29 Apr 2005 19:59:17 +0000 [thread overview]
Message-ID: <20050429195917.GA30999@vrfy.org> (raw)
In-Reply-To: <20050427173251.GA3575@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
On Wed, Apr 27, 2005 at 10:32:51AM -0700, Greg KH wrote:
> So, after much cursing and hand patching, I've converted the udev
> bitkeeper repository over to git. It can be now found at:
> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/udev.git
>
>
> To use it, get a copy of git or cogito or bit or whatever tool you want
> that works with git trees. To clone a local copy using cogito, you can
> do:
> cg-clone rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/udev.git
>
> and go from there.
>
> See one of the many git tutorials on the web, or on the git mailing list
> (at vger.kernel.org) if you have any questions on how to use git. I'm
> not going to be able to answer them myself, sorry.
>
> And if anyone wants to verify the udev git tree, to make sure I got it
> all right, please do. I know there is one dangling commit in there,
> that was due to a mixup on my part, you can safely ignore it.
>
> I'll figure out how to tag the different releases soon, and sign them
> too.
git does not support symlinks and therefore our test programs will fail.
Attached is a stupid script that creates the links in test/sys/ for the
tests to run again.
We should probably change git to support symlinks or move the sys/ tree
into a tarball...
And the permissions got lost during the conversion, but that does not
hurt much.
Thanks,
Kay
[-- Attachment #2: udev-symlinks.sh --]
[-- Type: application/x-sh, Size: 2342 bytes --]
prev parent reply other threads:[~2005-04-29 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 17:32 udev repo has changed to git Greg KH
2005-04-27 19:29 ` Kay Sievers
2005-04-29 19:59 ` Kay Sievers [this message]
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=20050429195917.GA30999@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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.