linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: udev repo has changed to git
Date: Wed, 27 Apr 2005 17:32:51 +0000	[thread overview]
Message-ID: <20050427173251.GA3575@kroah.com> (raw)

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.

thanks,

greg k-h


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2005-04-27 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 17:32 Greg KH [this message]
2005-04-27 19:29 ` udev repo has changed to git Kay Sievers
2005-04-29 19:59 ` Kay Sievers

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=20050427173251.GA3575@kroah.com \
    --to=greg@kroah.com \
    --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 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).