From: Sam Morris <sam@robots.org.uk>
To: grub-devel@gnu.org
Subject: Re: Moving to another SCM
Date: Mon, 18 Jun 2007 12:39:41 +0000 [thread overview]
Message-ID: <1182170381.646.11.camel@xerces> (raw)
In-Reply-To: 878xbabdju.fsf@xs4all.nl
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
> >> https://savannah.gnu.org/maintenance/Git
> >>
> >> It will depend on when savannah starts offering it when we can switch.
> >
> > Support for git is already up and running:
> > <http://git.savannah.gnu.org/gitweb/>. I know from the GNU coreutils and
> > gnulib people that they've already been using it successfully for a few
> > months. (``Successfully'' here means that they didn't regret to have
> > switched to git.)
>
> This sounds interesting. Personally I have no objections to a switch.
> Will the history be preserved, do we still have a commits mailinglist,
> is git easy to learn and how do other developers (especially Okuji)
> think about this?
I have been using the following script to maintain a mirror of Grub's
CVS repository. The first time it's run it creates a git repository in
'upstream'; subsequent runs will import any new commits since the last
run.
#!/bin/sh
set -e
export CVSROOT=:pserver:anonymous@cvs.savannah.gnu.org:/sources/grub
git-cvsimport -k -v -i -C upstream grub2
The full history, including branches, is imported. The 'upstream'
directory ends up being 6.3 MiB, which includes a checkout of the
'origin' branch.
--
Sam Morris
http://robots.org.uk/
PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-06-18 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 12:39 Sam Morris [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-21 18:38 Moving to another SCM Otavio Salvador
2007-05-22 18:52 ` Robert Millan
2007-05-22 21:58 ` Jeroen Dekkers
2007-05-27 12:13 ` Thomas Schwinge
2007-05-27 13:29 ` Marco Gerards
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=1182170381.646.11.camel@xerces \
--to=sam@robots.org.uk \
--cc=grub-devel@gnu.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.