bug-cvs
[Top][All Lists]
Advanced

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

CVSBookmarks and upstream submission


From: Christian Reis
Subject: CVSBookmarks and upstream submission
Date: Fri, 31 Jan 2003 13:48:24 -0200
User-agent: Mutt/1.2.5.1i

Hello there,

I've been using the CVSBookmarks patch (http://cvsbookmarks.sf.net/) for
quite some time now, and I'd like to discuss the merits of having it
sent upstream for inclusion in the main CVS codebase. 

The concept behind it is quite simple: it allows one to keep a
~/.cvsbookmarks file that provides a mapping between cvs repository
strings and a one-word key. This makes using CVS *much* easier when
dealing with multiple repositories, as happens with people that
contribute to many OSS projects, for instance. My current file looks
like this:

    gnome=:pserver:kiko@cvs.gnome.org:/cvs/gnome
    async=:pserver:kiko@async.com.br:/cvs
    zope=:pserver:anonymous@cvs.zope.org:/cvs-repository
    op=:ext:kiko_async@cvs.orbit-python.sourceforge.net:/cvsroot/orbit-python
    epydoc=:pserver:anonymous@cvs.epydoc.sourceforge.net:/cvsroot/epydoc
    lxr=:pserver:anonymous@cvs.lxr.sourceforge.net:/cvsroot/lxr
    mozilla=:pserver:kiko%async.com.br@cvs.mozilla.org:/cvsroot
    twisted=:ext:kiko@twistedmatrix.com:/cvs
    keithp=:pserver:anoncvs@keithp.com:/local/src/CVS

The author has been keeping the patch up to date, though because of the
latest security release it at the moment is doesn't apply cleanly. It's
a very useful feature and I'm sure others would appreciate it being
included, as it greatly improves the commandline client's usability.

Opinions? Has anybody evaluated or reviewed it in the past?

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL




reply via email to

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