[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Samizdat source code repository moves from CVS to Monotone

From: Dmitry Borodaenko
Subject: Samizdat source code repository moves from CVS to Monotone
Date: Wed, 10 Jun 2009 19:47:40 +0300

Greetings everyone,

The recent Savannah outage[0] has nearly wiped out Samizdat CVS
repository, among others. Thankfully, Savannah hackers have managed to
restore the data, but it doesn't mean that we will be so lucky next


This emergency is a final reminder that it's time to catch up with the
times and switch to a distributed version control system: among other
good things, a DVCS will allow developers and other users to keep an
up-to-date local copy of the whole history of the project development.

As of today, development of Samizdat moves from CVS to Monotone.[1]


Since Savannah doesn't support Monotone, the repository is hosted at To pull a copy of Samizdat repository into a new
local Monotone database and checkout the latest Samizdat code, do:

    mtn db init --db=~/
    mtn --db=~/ pull 'samizdat-*'
    mtn --db=~/ --branch=samizdat-head checkout samizdat

You might notice that the Monontone revision history is a bit more
fine-grained than that in CVS. That would be because since May 2005, I
used Monotone to track my changes to Samizdat, and manually propagated
these to the public CVS repository. CVS sync points are marked in
Monotone revision history with "CVS <Y-m-d>" commit messages.

I will no longer do that: CVS repository will remain available for some
time in frozen state, and after a while will disappear off the face of
the Net. I will, however, maintain a Git mirror of Monotone repository
at Savannah[2] using Monotone git_export command.


The Git mirror is just a convenience for people who know Git and don't
want to figure out Monotone, or who want to use fancy tools that are
only available for Git, or who, like myself, find ViewMTN web interface
awkward in comparison to cgit. It is by no means a way to commit changes
to Samizdat: the only way it can be updated is mtn git_export.

The way to commit changes to Samizdat is to send me your `mtn pubkey`
and stake out a private branch namespace starting with
samizdat-dev-<yourname>. The way to propagate changes from there to
samizdat-head is to propose a merge on this mailing list or in Savannah

As always, feedback is welcome!

Dmitry Borodaenko

reply via email to

[Prev in Thread] Current Thread [Next in Thread]