From: Michael Koch <konqueror@gmx.de>
To: Robert Schuster <theBohemian@gmx.net>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: future plans for mauve
Date: Fri, 29 Oct 2004 10:59:00 -0000 [thread overview]
Message-ID: <200410291259.48230.konqueror@gmx.de> (raw)
In-Reply-To: <41822114.1020602@gmx.net>
Am Freitag, 29. Oktober 2004 12:53 schrieb Robert Schuster:
> Hi
>
> >>* Package structure. The part that could be called the 'testlet
> >>api' should live in gnu.testlet. The test runner implementation
> >>should be in gnu.mauve.runner (?) and test hierarchy perhaps in
> >>gnu.mauve.tests.
> >
> >Mauving things around in CVS is a bad idea as the history of
> > changes for the moved files get lost. I often look into such
> > informations.
>
> Maybe this was an implicit wish to switch to SVN?
> They have a nice CVS2SVN conversion tool at tigris.org, too:
> http://cvs2svn.tigris.org/
I would like monotone more [1]. It can import CVS history too and is
much more capable of distributed development and has better merging
support. Perhaps someone does a drive while I'm in holiday ...
Michael
[1] http://www.venge.net/monotone/
--
Homepage: http://www.worldforge.org/
prev parent reply other threads:[~2004-10-29 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 6:41 Noa Resare
2004-10-29 6:51 ` Michael Koch
[not found] ` <41822114.1020602@gmx.net>
2004-10-29 10:59 ` Michael Koch [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200410291259.48230.konqueror@gmx.de \
--to=konqueror@gmx.de \
--cc=mauve-discuss@sources.redhat.com \
--cc=theBohemian@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).