[IPython-dev] A maze of twisty little version control systems, mostly alike (Was [Fwd: Re: making pdoc, pdef, ) and pinfo more generally useful]

R. Bernstein rocky at panix.com
Fri Oct 13 13:14:20 EDT 2006

First, thanks everyone for the suggestions on how to apply version
control on top of another version control system.

>From Stefan van der Walt's suggestion and help (sent in private
email), I have bzr running on top of the ipython svn. So the problem I
was having with backed-up patches shouldn't be an issue in the
future. Thanks Stefan v.d.W!

However I will also look into Mercurial Queues as suggested by Stefan
Reichoer. I currently use SVN, CVS, Perforce, RCS, SCCS (in the past),
and now bzr. Other than bitkeeper and GNU Arch, I wasn't aware there
*were* any more version control systems. I can't wait for a half a
dozen more to come on the scene so we can learn those as well.

But also many thanks to Stefan Reichoer thanks for mentioning and
writing dvc. I've installed that. (One little suggestion though for
the INSTALL file. A small step is missing if you get the package via
"bzr get http://bzr.xsteve.at/dvc" - I needed to run autoconf to build
configure from configure.ac)

I also noticed that Stefan R. has also written an Emacs SVN interface
too! As a PCL-CVS user This is something I've long wanted. (And it had
not escaped my careful and keep powers of observation that ipython
uses SVN.)

In sum, I'm learning a great deal from reading the ipython-dev forum.

Again - thanks.

Fernando Perez writes:
 > Thanks for the suggestions.  Note that I'm forwarding this manually to the 
 > list since it discards non-subscriber posts (too much spam).
 > Cheers,
 > f
 > -------- Original Message --------
 > Subject:
 > Re: making pdoc, pdef, and pinfo more generally useful
 > From:
 > Stefan Reichör <stefan at xsteve.at>
 > Date:
 > Fri, 13 Oct 2006 11:13:28 +0200
 > To:
 > ipython-dev at scipy.net
 > "Ville M. Vainio" <vivainio at gmail.com> writes:
 >  > > On 10/12/06, R. Bernstein <rocky at panix.com> wrote:
 >  > >
 >  >> >> I didn't do this initially because, well, I'm currently backed up in
 >  >> >> patches, what I have works and I don't want to destroy that, and
 >  >> >> adding my own version control on top of SVN checked-out sources is a
 >  >> >> bit whacky.
 >  > >
 >  > > Not really all that whacky, esp. if the svn is for the "official,
 >  > > stable version" that is expected to work rather predictably. Too bad
 >  > > svn is not a distributed vcs...
 >  > >
 >  > > I recommend bzr (bazaar-ng) for your "own", on-top-of-svn version
 >  > > control, works really well with local versions of files and no need
 >  > > for repository administration.
 >  > >
 >  > > See http://doc.bazaar-vcs.org/bzr.dev/tutorial.htm if you are interested.
 > I also think that bzr is a good solution for that kind of stuff.
 > However, I use Mercurial Queues (mq) for tracking svn repositories and
 > generating patches.
 > Since R. Bernstein uses Emacs, let me do some advertisement for emacs dvc:
 > http://www.xsteve.at/prg/emacs_dvc/index.html
 > I have added emacs support for mq. That way I can easily build patches
 > for upstream projects.
 > If anyone would like to try this setup, feel free to ask  ;-)
 > Stefan.

More information about the IPython-dev mailing list