ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: [Fwd: Bug tracking system for ConTeXt]
Date: Thu, 28 Feb 2002 23:28:54 +1100	[thread overview]
Message-ID: <87r8n5dc3d.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <5.1.0.14.1.20020227214357.03ee1570@server-1> (Hans Hagen's message of "Wed, 27 Feb 2002 21:46:51 +0100")

On Wed, 27 Feb 2002, Hans Hagen wrote:
> At 12:07 AM 2/28/2002 +1100, Daniel Pittman wrote:
> 
> Thanks for the explanation!

Is the case of aegis, take it with a bit of a grain of salt. A couple of
people have pointed out to me that I might be less aware of it's
features than I thought.

It's also the one I know the least about so your millage may vary.

>> > - aegis (http://aegis.sourceforge.net/)
>>
>>Unless I am very much mistaken this is a development process tool that
>>works with your choice of revision control system and imposes
>>additional process on it.
>>
>>Last I checked it talked about RCS, CVS and SCCS, but may support
>>more.
>>
>>This may be a solution to problems of greater scope than revision
>>control, which may actually be the problem you are trying to address
>>here, but it's not, in and of itself, a revision control system.
> 
> Does anyone know perforce (commercial)? TeX live is done with it.

I have heard good things about it but only very indirectly. It's
commercial nature made it hard to verify experimentally as we didn't
manage to secure a test license in the period I was looking.

        Daniel

-- 
A cathedral, a wave of a storm, a dancer's leap,
never turn out to be as high as we had hoped.
        -- Marcel Proust


  parent reply	other threads:[~2002-02-28 12:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 12:50 Tobias Burnus
2002-02-27  0:33 ` Marko Schuetz
2002-02-27 11:23   ` Tobias Burnus
2002-02-27 13:07     ` Daniel Pittman
2002-02-27 14:24       ` Marko Schuetz
2002-02-27 20:46       ` Hans Hagen
2002-02-28 10:57         ` Berend de Boer
2002-02-28 12:28         ` Daniel Pittman [this message]
2002-02-28 16:48           ` Hans Hagen
2002-02-27 14:24     ` Marko Schuetz

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=87r8n5dc3d.fsf@inanna.rimspace.net \
    --to=daniel@rimspace.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 NNTP newsgroup(s).