[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [525] update, drop dead links, refine text
|
From: |
ineiev |
|
Subject: |
[Savannah-cvs] [525] update, drop dead links, refine text |
|
Date: |
Fri, 3 Feb 2023 03:12:13 -0500 (EST) |
Revision: 525
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=525
Author: ineiev
Date: 2023-02-03 03:12:12 -0500 (Fri, 03 Feb 2023)
Log Message:
-----------
update, drop dead links, refine text
Modified Paths:
--------------
trunk/sviki/GNUArch.mdwn
trunk/sviki/Hg.mdwn
trunk/sviki/JustSFTP.mdwn
trunk/sviki/MonoToNe.mdwn
trunk/sviki/SvN.mdwn
trunk/sviki/SvnImportExistingRepo.mdwn
trunk/sviki/UsingBzr.mdwn
trunk/sviki/UsingGnuArch.mdwn
trunk/sviki/UsingHg.mdwn
Modified: trunk/sviki/GNUArch.mdwn
===================================================================
--- trunk/sviki/GNUArch.mdwn 2023-02-02 11:11:12 UTC (rev 524)
+++ trunk/sviki/GNUArch.mdwn 2023-02-03 08:12:12 UTC (rev 525)
@@ -1,10 +1,10 @@
-The Arch Subsystem
-------------------
+# GNU Arch: notes for admins
-GNU Arch is supported at
-<http://arch.sv.gnu.org/> on Savannah's Arch
-subsystem.
+## The Arch Subsystem
+[GNU Arch](http://arch.sv.gnu.org/) is supported
+on Savannah's Arch subsystem.
+
All Savannah Arch-related materials are located in the Savannah
Administration's Arch repository.
`sftp://arch.sv.gnu.org/administration`
@@ -15,21 +15,18 @@
- arch-webpage--production--1.0 -- the webpage on arch.sv.gnu.org
- infra--main--0 -- scripts that describe how Savannah is setup
-Creating an Archive
--------------------
+## Creating an Archive
The archive is created via the backend when the admin activates the
feature in Savane.
-[[ArchZoom]]
-------------
+## ArchZoom
-[[ArchZoom]] is installed but needs frontend/backend mods to 1)
-reference available archives and 2) registers/removes them from the
-[[ArchZoom]]'s `~/.arch-params/=locations`.
+ArchZoom is installed but needs frontend/backend mods to 1)
+reference available archives and 2) registers/removes them from
+`~/.arch-params/=locations`.
-Naming convention
------------------
+## Naming convention
There used to be a naming convention where only one archive was created
at the top-level, but now since users did not follow it (to be able to
@@ -39,8 +36,7 @@
archives (such as the [[ArchZoom]] archive registration above) but it's
far more convenient for users.
-Signatures
-----------
+## Signatures
We should encourage, but not enforce the use of signatures. Checking
signatures is a difficult matter, especially with expired/revoked keys.
@@ -47,13 +43,8 @@
Check bug-cvs archives (2005-08 to 2005-10) for interesting GPG-signed
commits discussions.
-<http://ximbiot.com/cvs/wiki/index.php?title=GPG-Signed_Commits>
-should centralize the information, but everything is rather in the
-mailing lists atm.
+## Obsolete - commit Notifications
-Obsolete - commit Notifications
--------------------------------
-
At a point we had a modified SSH server that allowed to send commit
notifications. Since GNU Arch is not meant to be used through an
intelligent server we disabled this and repositories are not accessed
@@ -69,13 +60,8 @@
`email-on-commit savannah-cvs@gnu.org`
-Outdated - updating the webpage
--------------------------------
+## Outdated - updating the webpage
The arch.sv.gnu.org webpage was managed via
administration@sv.gnu.org/arch-webpage--production--1.0 but it's easier
to modify the webpage as root.
-
-#### subtopics:
-
-- [[ArchZoom]]
Modified: trunk/sviki/Hg.mdwn
===================================================================
--- trunk/sviki/Hg.mdwn 2023-02-02 11:11:12 UTC (rev 524)
+++ trunk/sviki/Hg.mdwn 2023-02-03 08:12:12 UTC (rev 525)
@@ -1,9 +1,8 @@
-Documentation
--------------
+# Mercurial: notes for admins
-### SSH access
+## SSH access
-<http://www.selenic.com/mercurial/wiki/index.cgi/SharedSSH>
+<https://www.selenic.com/mercurial/wiki/index.cgi/SharedSSH>
This method looks a bit rusty though.
@@ -11,7 +10,7 @@
in push/pull mode only (no repository creation since we want hooks to be
controlled by us).
-### Web browsing
+## Web browsing
It's done through hgwebdir.wsgi
@@ -18,19 +17,9 @@
Since Mercurial 1.0, mod\_wsgi shall be used for the web interface
(older Mercurial versions crashed):
-- <http://www.selenic.com/mercurial/wiki/index.cgi/modwsgi>
+- <https://www.selenic.com/mercurial/wiki/index.cgi/modwsgi>
Old instructions for mod\_python:
-- <http://www.newartisans.com/blog_files/mercurial.with.mod_python.php>
- and
- <http://www.selenic.com/pipermail/mercurial/2007-May/013226.html>
+- <https://www.selenic.com/pipermail/mercurial/2007-May/013226.html>
(mod\_python)
--
<http://blog.sietch-tabr.com/index.php/post/2008/01/21/Mercurial-:-partage-de-depots-differents-en-http-et-https-push-par-https>
- (CGI)
-
-Existing hosting
-----------------
-
-- <http://freehg.org/> with its source code
- <http://freehg.org/u/mmarshall/freehg/>
Modified: trunk/sviki/JustSFTP.mdwn
===================================================================
--- trunk/sviki/JustSFTP.mdwn 2023-02-02 11:11:12 UTC (rev 524)
+++ trunk/sviki/JustSFTP.mdwn 2023-02-03 08:12:12 UTC (rev 525)
@@ -1,12 +1,11 @@
-Why not providing a simple SFTP account for new VCS?
+Why not provide a simple SFTP account for new VCS?
-- If we provide a simple sftp account then everybody can remove the
- project history; we don't want that because
+- If we provide a simple sftp account then any group member will
+ be able to remove source history; we don't want that because
1. We want source code to stay available even if, say, a piece of
- software decide to go proprietary and remove existing Savannah
- sources
- 2. Project admins won't like intentional or unintentional
- repository irremediable deletion/corruption by new project
+ software decides to go proprietary and remove existing sources.
+ 2. Group admins won't like intentional or unintentional
+ repository irremediable deletion/corruption by new group
members. We should be able to work around that.
- This may help supporting new SCMs, but this actually requires more
Modified: trunk/sviki/MonoToNe.mdwn
===================================================================
--- trunk/sviki/MonoToNe.mdwn 2023-02-02 11:11:12 UTC (rev 524)
+++ trunk/sviki/MonoToNe.mdwn 2023-02-03 08:12:12 UTC (rev 525)
@@ -1,32 +1,28 @@
+# (No) Monotone at Savannah
+
(There are no request to support monotone and thus no plans to do so. --2015)
-Monotone now probably can be used for mass hosting:
----------------------------------------------------
+## Monotone now probably can be used for mass hosting:
- ssh support (read/write) - since 0.27/2006-06
- multi-database server (read) - since 0.23/2005-09
-<http://mtn-host.prjek.net/> demonstrates
-Monotone hosting and publishes its source code (project `webhost`)
-
Technically, usher can be used for write access, but does not support
privileges separation (one uid must have write access to all repos).
-References
-----------
+## References
-There was a discussion about supporting montone at Savannah it on the
-monotone-devel list (hosted by Savannah :)) last year:
-<http://lists.gnu.org/archive/html/monotone-devel/2005-08/msg00072.html>
+A [discussion about supporting montone at
+Savannah](//lists.gnu.org/archive/html/monotone-devel/2005-08/msg00072.html)
+on the monotone-devel list (hosted by Savannah :)).
-Monotone proselitism ;) by Chad Walstrom:
-<http://lists.gnu.org/mailman/private/gnu-prog-discuss/2006q2/001201.html>
+[Monotone
+proselitism](//lists.gnu.org/mailman/private/gnu-prog-discuss/2006q2/001201.html)
+;) by Chad Walstrom.
-(For more general discussion about supporting a new service, check
-[[NewServiceSupport]])
+[[More general discussion about supporting new services|NewServiceSupport]].
-Rejected Ideas
---------------
+## Rejected ideas
- usher + setuid wrapper for 'mtn server': I think the authentication
is performed after `mtn server` is started
Modified: trunk/sviki/SvN.mdwn
===================================================================
--- trunk/sviki/SvN.mdwn 2023-02-02 11:11:12 UTC (rev 524)
+++ trunk/sviki/SvN.mdwn 2023-02-03 08:12:12 UTC (rev 525)
@@ -1,61 +1,27 @@
+Subversion at Savannah
+======================
+
Locations
---------
-- svn+ssh://YOU@svn.sv.gnu.org/PROJECT - write access for project members
-- svn://svn.sv.gnu.org/PROJECT - anonymous access
-- <http://svn.sv.gnu.org/svn/PROJECT> - slow readonly access for people
+- svn+ssh://YOU@svn.sv.gnu.org/GROUP - write access for group members
+- svn://svn.sv.gnu.org/GROUP - anonymous access
+- http://svn.sv.gnu.org/svn/GROUP - slow readonly access for people
who can't talk their admin into allowing outgoing SVN access
-- <http://svn.sv.gnu.org/viewvc/?root=PROJECT>
-- `vcs0:/srv/svn/PROJECT` - actual host location, for admins
+- http://svn.sv.gnu.org/viewvc/?root=GROUP
+- vcs0:/srv/svn/GROUP - actual host location, for admins
Documentation
-------------
-- The SVN book at
- <http://svnbook.red-bean.com/>
-- Tips at BerliOS:
-
<http://developer.berlios.de/docman/display_doc.php?docid=394&group_id=2#convert>
-- The documentation from Gna!
- (<https://gna.org/svn/?group=savane>,
- <https://gna.org/cookbook/?group=admin#svn>)
-- CVS to SVN conversion: see [[CvSToSvN]].
+- [The SVN book](http://svnbook.red-bean.com/).
+- [[For Savannah admins: CVS to SVN conversion|CvSToSvN]].
Commit Email
------------
-For users: please submit a support request, including the project name
+For users: please submit a support request, including the group name
and the email address to send commits to.
-For admins: there is a script `vcs0:/usr/local/bin/svn-commit-email` to
+For admins: there is a script vcs0:/usr/local/bin/svn-commit-email to
create the (boilerplate) post-commit hook.
-
-SVK
----
-
-SVK add a distributed layer on top of SVN. You can find an introduction
-and an example at [[SavaneSvkBranch]]. SVK is a Perl tool built on top
-of SVN, and provides, among others, distributed features. It doesn't
-need a custom server, it just uses the SVN one, which sounds quite good.
-It's darn slow.
-
-Signatures
-----------
-
-SVK provides the -S option to GPG-sign commits. A simple direct SVK
-mirror could do the trick to seamlessly sign commits. However,
-<http://svk.elixus.org/?SVKSucks> says:
-
- svk signature is appended after the commit is done. this sucks because you
cannot check the signature before accepting the commit on the server side.
- This also sucks because it leads to complex scripting and race condition
on the server side, if you verify signatures.
-
-Links to 3rd-party utilities
-----------------------------
-
-- <http://subversion.tigris.org/project_links.html>
-- <http://svnbook.red-bean.com/en/1.1/apds03.html>
-
-Other links
------------
-
-- SF.net supports SVN since feb. 2006:
- <https://sourceforge.net/docs/E09/>
Modified: trunk/sviki/SvnImportExistingRepo.mdwn
===================================================================
--- trunk/sviki/SvnImportExistingRepo.mdwn 2023-02-02 11:11:12 UTC (rev
524)
+++ trunk/sviki/SvnImportExistingRepo.mdwn 2023-02-03 08:12:12 UTC (rev
525)
@@ -1,33 +1,30 @@
+# Importing Subversion repository
+
If you want to import your existing SVN repository at Savannah
(preserving all history):
-- Prepare a dump (see below):
+- Prepare a dump:
- svnadmin dump myproject-svn/ | bzip2 > myproject-dump.bz2
+ svnadmin dump mygroup-svn/ | bzip2 > mygroup-dump.bz2
- Upload it at Savannah (using your download area at
- download.savannah.gnu.org or download.savannah.nongnu.org):
+ download.savannah.nongnu.org):
- scp myproject-dump.bz2 mylogin@dl.sv.gnu.org:/srv/download/myproject/
+ scp mygroup-dump.bz2 mylogin@dl.sv.nongnu.org:/srv/download/mygroup/
Or anywhere else that is convenient.
-- Enable SVN for your project (in Main -\> Select Features from your
- project page)
+- Enable SVN for your group (in Main -\> Select Features from your
+ group page)
- Post a support request and specify where your dump was uploaded:
<http://savannah.gnu.org/support/?group=administration>
-The Savannah Hackers will then import it on the system (Savannah
-hackers: see [[AdminSvnImport]])
+Savannah Hackers will then [[import it on the system|AdminSvnImport]].
Do not send a tar.gz of your SVN repository. Using a dump is important
because it's independent of the subversion release.
Note: if you just want to upload your initial source code, not your
-whole project history, just use `svn add` and commit.
-
-#### subtopics:
-
-- [[AdminSvnImport]]
+whole group history, just use `svn add` and commit.
Modified: trunk/sviki/UsingBzr.mdwn
===================================================================
--- trunk/sviki/UsingBzr.mdwn 2023-02-02 11:11:12 UTC (rev 524)
+++ trunk/sviki/UsingBzr.mdwn 2023-02-03 08:12:12 UTC (rev 525)
@@ -1,7 +1,9 @@
-This page is for using bzr on Savannah. If you are here to learn how
-to use Bazaar in general please see the upstream documentation:
-<http://wiki.bazaar.canonical.com/Tutorials>
+# GNU Bazaar at Savannah
+This page is for using bzr at Savannah. If you are here to learn how
+to use Bazaar in general, please see the
+[upstream documentation](//wiki.bazaar.canonical.com/Tutorials)
+
(Note: if you're using Bazaar 2.3 or earlier, your "real name" in your
Savannah profile must not contain non-ASCII characters, so that the push
command works:
@@ -14,23 +16,23 @@
----------------------------------------
bzr init-repository bzr+ssh://YOU@bzr.sv.gnu.org/testyten/
- cd YOUR_PROJECT/
+ cd YOUR_GROUP/
bzr init
bzr add .
bzr commit -m "Initial import"
- bzr push bzr+ssh://YOU@bzr.sv.gnu.org/YOUR_PROJECT/
+ bzr push bzr+ssh://YOU@bzr.sv.gnu.org/YOUR_GROUP/
Initial import - single branch repository
-----------------------------------------
- cd YOUR_PROJECT/
+ cd YOUR_GROUP/
bzr init
bzr add .
bzr commit -m "Initial import"
- bzr push bzr+ssh://YOU@bzr.sv.gnu.org/YOUR_PROJECT/YOUR_BRANCH/
+ bzr push bzr+ssh://YOU@bzr.sv.gnu.org/YOUR_GROUP/YOUR_BRANCH/
GUIs
----
There are a few graphical user interfaces for Bazaar; the standard one
-is the [Bazaar Explorer](http://doc.bazaar.canonical.com/explorer/en/).
+is the [Bazaar Explorer](//doc.bazaar.canonical.com/explorer/en/).
Modified: trunk/sviki/UsingGnuArch.mdwn
===================================================================
--- trunk/sviki/UsingGnuArch.mdwn 2023-02-02 11:11:12 UTC (rev 524)
+++ trunk/sviki/UsingGnuArch.mdwn 2023-02-03 08:12:12 UTC (rev 525)
@@ -1,6 +1,7 @@
-Help yourself!
---------------
+# GNU Arch at Savannah
+## Help yourself!
+
Newest versions of Arch include *A GNU Arch Handbook*, which covers the
basics. It is not currently available online, so grab it from your GNU
Arch sources in `src/docs-tla/`.
@@ -15,27 +16,26 @@
# Show help about a specific command:
tla <command> -H # e.g.: tla my-id -H
-*arch Meets hello-world - A Tutorial Introduction to The arch Revision
-Control System* covers advanced use, especially the different ways to
+[arch Meets hello-world - A Tutorial Introduction to The arch Revision
+Control System](//www.gnu.org/software/gnu-arch/tutorial-old/arch.html)
+covers advanced use, especially the different ways to
use branching (decentralised development, cherry-picking...). It begins
-to be outdated, but the concepts still apply. Check it at:
-<http://www.gnu.org/software/gnu-arch/tutorial-old/arch.html>.
-A new version is in progress at
-<http://www.gnu.org/software/gnu-arch/tutorial/>
+to be outdated, but the concepts still apply.
+A [new version](//www.gnu.org/software/gnu-arch/tutorial/) is in progress.
+
Here, we provide Savannah-specific information, as well as references to
more complete documentation.
-Setting up GNU Arch
--------------------
+## Setting up GNU Arch
### Creating the archive
You need to do something like:
- tla make-archive sftp://arch.sv.gnu.org/archives/yourproject/myarchive1
+ tla make-archive sftp://arch.sv.gnu.org/archives/your_group/myarchive1
-Alternatively, if you want to use `/archives/yourproject/` as your
+Alternatively, if you want to use `/archives/your_group/` as your
archive, and since tla currently doesn't want to create archive in
existing repositories, you can bypass this limitation by using
`tla make-archive` locally and upload it to the server using sftp. Or
@@ -48,9 +48,9 @@
# Tell Arch who you are:
tla my-id "FirstName LastName <your@email.tld>"
# Tell Arch where your archive is:
- tla register-archive
sftp://your_username@arch.sv.gnu.org/archives/your_project
+ tla register-archive
sftp://your_username@arch.sv.gnu.org/archives/your_group
# Tell Arch to use that archive by default:
- tla my-default-archive your_project@sv.gnu.org
+ tla my-default-archive your_group@sv.gnu.org
### Initial import
@@ -58,9 +58,9 @@
future version of GNU Arch. For now the following should help:
# Go in your current sources directory:
- cd project_directory-X.Y.Z
+ cd group_directory-X.Y.Z
# Add GNU Arch administrivia ({arch}):
- tla init-tree your_project--main--0
+ tla init-tree your_group--main--0
# Tell GNU Arch which files to import ("register files"):
tla inventory --names --source --both --unescaped \
| tr '\n' '\000' \
@@ -78,7 +78,7 @@
If you have no file to import, the procedure is simpler:
# Create the project in the Arch archive:
- tla archive-setup your_project--main--0
+ tla archive-setup your_group--main--0
You then can get an (empty) Arch-enabled working copy as usual - see
next section.
@@ -89,8 +89,7 @@
present a set of nifty tools for GNU Arch. Debian package is
`tla-tools`.
-Get a working copy of your archive
-----------------------------------
+## Get a working copy of your archive
When you need to work on your project, you need to get an Arch-enabled
working copy. It will include, among others, file identifiers that will
@@ -98,18 +97,17 @@
track its history:
# Get a project in your default archive:
- tla get your_project--main--0 destination_directory
+ tla get your_group--main--0 destination_directory
If you want to grab a working copy from another archive, you need to
specify it explicitely:
- tla get -A other_project@sv.gnu.org another_project--mainline--1.0
destination_directory
+ tla get -A other_group@sv.gnu.org another_group--mainline--1.0
destination_directory
(alternatively you could change your default archive with
`tla my-default-archive`)
-Working with GNU Arch
----------------------
+## Working with GNU Arch
### Get the work from your co-workers
@@ -197,12 +195,11 @@
GPG passphrase, and get `unable to acquire revision lock`), break the
archive lock:
- tla lock-revision --break your_project--main--0--patch-X
+ tla lock-revision --break your_group--main--0--patch-X
and then commit again.
-Signing
--------
+## Signing
### Setting-up signatures auto-checking
@@ -259,9 +256,9 @@
Here we sign an unsigned repository with your own key:
- tla make-archive --listing --signed --mirror project@sv.gnu.org
/tmp/archive/
- tla archive-mirror project@sv.gnu.org
- tla register-archive -d project@sv.gnu.org-MIRROR
+ tla make-archive --listing --signed --mirror group@sv.gnu.org
/tmp/archive/
+ tla archive-mirror group@sv.gnu.org
+ tla register-archive -d group@sv.gnu.org-MIRROR
rm /tmp/archive/=meta-info/mirror
[[ToDo]]: now is it possible to upload the result directly at Savannah,
@@ -272,8 +269,7 @@
-
<http://web.archive.org/web/20070808210801/http://www.gnuarch.org/gnuarchwiki/Signing_Archives#head-af0d7652a6fb03610c15fd099b31a2a92be98447>
-
<http://web.archive.org/web/20070205172249/http://www.gnuarch.org/gnuarchwiki/mini_MirroringArchives>
-Tuning
-------
+## Tuning
### Activate the cache
@@ -319,8 +315,7 @@
killall ssh
-Converting a CVS repository to GNU Arch
----------------------------------------
+## Converting a CVS repository to GNU Arch
Check
<http://web.archive.org/web/20080503104335/http://www.gnuarch.org/gnuarchwiki/cscvs>.
@@ -328,13 +323,11 @@
conversion":
<http://web.archive.org/web/20080427163916/http://www.gnuarch.org/gnuarchwiki/Arch%20and%20CVS%20in%20the%20same%20tree#head-aaa33a25bb0ce260a057294498b0dfeddf3dcb24>
-Installing the latest GNU Arch on Debian Sarge
-----------------------------------------------
+## Installing the latest GNU Arch on Debian Sarge
<http://dl.savannah.gnu.org/releases/arch4debian/sarge-backports/>
-Grab the latest source code
----------------------------
+## Grab the latest source code
You can use a tarball from
<http://ftp.gnu.org/old-gnu/gnu-arch/>
Modified: trunk/sviki/UsingHg.mdwn
===================================================================
--- trunk/sviki/UsingHg.mdwn 2023-02-02 11:11:12 UTC (rev 524)
+++ trunk/sviki/UsingHg.mdwn 2023-02-03 08:12:12 UTC (rev 525)
@@ -1,11 +1,12 @@
-URL-s summary:
+Mercurial at Savannah
+=====================
-- <ssh://hg.sv.gnu.org/project> -
- developer access using SSH
-- <http://hg.sv.gnu.org/hgweb/project>
- - lightweight http-based protocol (read-only access)
+URL summary:
-Web browser: <http://hg.sv.gnu.org/hgweb/>
+- ssh://hg.sv.gnu.org/*group* - developer access using SSH
+- http://hg.sv.gnu.org/hgweb/*group* - lightweight http-based protocol
+ (read-only access)
+- [Web viewer](//hg.savannah.gnu.org/hgweb/)
Basic commands
--------------
@@ -12,17 +13,17 @@
- Checkout with authentication:
- hg clone ssh://login@hg.sv.gnu.org/project
+ hg clone ssh://login@hg.sv.gnu.org/group
For the SSH key fingerprints for hg.sv.gnu.org, check
the "Mercurial Repository" link under "Development Tools"
- on the main page of your project.
+ on the main page of your group.
- Checkout with anonymous read-only access:
- hg clone http://hg.sv.gnu.org/hgweb/project
+ hg clone http://hg.sv.gnu.org/hgweb/group
or
- hg clone https://hg.sv.gnu.org/hgweb/project
+ hg clone https://hg.sv.gnu.org/hgweb/group
Developer setup
---------------
@@ -33,7 +34,7 @@
[ui]
username = Your Name Comes Here <you@yourdomain.example.com>
-It is also possible to edit per project identity (project/.hg/hgrc).
+It is also possible to edit per group identity (group/.hg/hgrc).
Developer basic commands
------------------------
@@ -50,7 +51,7 @@
hg commit -m "Initial import"
# initial publication to Savannah
- hg push ssh://login@hg.sv.gnu.org/project
+ hg push ssh://login@hg.sv.gnu.org/group
Note: at this point your repository is not setup to merge \_from\_
the remote branch when you type 'hg pull'. You can either freshly
@@ -57,18 +58,18 @@
'clone' the repository (see "Developer checkout" below), or
configure your current repository this way:
- Edit project/.hg/hgrc:
+ Edit group/.hg/hgrc:
[paths]
- default = ssh://you@hg.sv.gnu.org/project
+ default = ssh://you@hg.sv.gnu.org/group
- Developer checkout:
- hg clone ssh://login@hg.sv.gnu.org/project
+ hg clone ssh://login@hg.sv.gnu.org/group
- Commit:
- cd project/
+ cd group/
# <edit some_existing_file>
hg commit -m "I automatically commit modified files"
@@ -98,7 +99,7 @@
------------------------
Mercurial has a [convert
-extension](http://www.selenic.com/mercurial/wiki/index.cgi/ConvertExtension)
+extension](https://www.selenic.com/mercurial/wiki/index.cgi/ConvertExtension)
that supports multiple repository types (CVS, Subversion, GNU Arch, Git,
darcs...).
@@ -108,15 +109,10 @@
[extensions]
hgext.convert =
-The conversion tool is the same for all the different repository types
-(check the [convert
-extension](http://www.selenic.com/mercurial/wiki/index.cgi/ConvertExtension)
-for specific tweaks):
+ hg convert group
+ cd group-hg
+ hg push ssh://login@hg.sv.gnu.org/group
- hg convert project
- cd project-hg
- hg push ssh://login@hg.sv.gnu.org/project
-
- **CVS** conversion will also maintain CVS tags.
- **GNU Arch** conversion does not handle multiple branches or version
numbers, thus it only works for a given *category--branch--version*.
@@ -124,9 +120,6 @@
Links
-----
-- <http://www.selenic.com/mercurial/>
- - Mercurial's site
-- <http://hgbook.red-bean.com/hgbook.html>
- - Mercurial's book
-- <http://www.selenic.com/mercurial/wiki/index.cgi/Tutorial>
- - Tutorial
+- [Mercurial site](https://www.selenic.com/mercurial/)
+- [Mercurial book](http://hgbook.red-bean.com/hgbook.html)
+- [Tutorial](https://www.selenic.com/mercurial/wiki/index.cgi/Tutorial)
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [525] update, drop dead links, refine text,
ineiev <=