[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: please migrate to git
From: |
Gavin Smith |
Subject: |
Re: please migrate to git |
Date: |
Sun, 25 Nov 2018 20:56:22 +0000 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
> > * The main branch is called "trunk" and not "master". (This is probably
> > why pushing worked - there was no branch already existing called
> > "trunk".) The "master" branch is the old 10 years-out-of-date mirror. I
> > believe it is possible to delete the master branch and rename "trunk" to
> > "master", although there may be problems with what Savannah allows. On
> > https://savannah.gnu.org/support/?109326 the Savannah maintainers said
> > that the "master" branch couldn't be reverted.
> All branches should be moved out of refs/heads/bare/* into refs/heads/*.
I believe the branches should be cleared up now. Apparently "git svn"
creates them all as git branches when they should really be git tags.
> The metadata uses svn://127.0.0.1/svn_repo/ instead of
> svn://svn.savannah.gnu.org/. You can use --rewrite-root to fix that.
I believe I have changed the svn URL. The output of "git svn info":
$ git svn info
Path: .
URL: svn://127.0.0.1/svn_repo/texinfo/trunk
Repository Root: svn://svn.savannah.gnu.org/texinfo
Repository UUID: 39fee189-59d7-47db-b5d4-205258b72aed
Revision: 8445
Node Kind: directory
Schedule: normal
Last Changed Author: Gavin Smith
Last Changed Rev: 8445
Last Changed Date: 2018-11-25 20:12:04 +0000 (Sun, 25 Nov 2018)
I'm not sure if this is updated on Savannah or just on my version.
When this conversion is definitely finished, I intend to remove this
metadata and disable the SVN repository on Savannah.
All the git commit messages reference the SVN versions, e.g.
git-svn-id: svn://127.0.0.1/svn_repo/texinfo/address@hidden
39fee189-59d7-47db-b5d4-205258b72aed
It would be nice to change the URL to svn://svn.savannah.gnu.org/
instead just so it is clear where it came from.
https://git.wiki.kernel.org/index.php/GitSvnSwitch implies this is
possible but it links to a non-existent blog to explain how to do it.
- Re: please migrate to git, (continued)
Re: please migrate to git, Gavin Smith, 2018/11/19
- Re: please migrate to git, Werner LEMBERG, 2018/11/19
- Re: please migrate to git, Masamichi Hosoda, 2018/11/20
- Re: please migrate to git, Gavin Smith, 2018/11/24
- Re: please migrate to git, Norbert Preining, 2018/11/24
- Re: please migrate to git, Gavin Smith, 2018/11/25
- Re: please migrate to git, Andreas Schwab, 2018/11/25
- Re: please migrate to git,
Gavin Smith <=
- Re: please migrate to git, Andreas Schwab, 2018/11/25
- Re: please migrate to git, Gavin Smith, 2018/11/26
Re: please migrate to git, Eli Zaretskii, 2018/11/25
Re: please migrate to git, Gavin Smith, 2018/11/25
Re: please migrate to git, Eli Zaretskii, 2018/11/25
Re: please migrate to git, Gavin Smith, 2018/11/26
Re: please migrate to git, Gavin Smith, 2018/11/25
Re: please migrate to git, Gavin Smith, 2018/11/24