all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Manoj Srivastava <srivasta@ieee.org>
To: emacs-devel@gnu.org
Subject: Re: Manual policy (Re: Emacs-devel Digest, Vol 44, Issue 65)
Date: Wed, 10 Oct 2007 17:00:00 -0500	[thread overview]
Message-ID: <87641e4om7.fsf@anzu.internal.golden-gryphon.com> (raw)
In-Reply-To: 20071010214419.GA1297@thyrsus.com

On Wed, 10 Oct 2007 17:44:19 -0400, Eric S Raymond <esr@thyrsus.com> said: 

> From: Jason Rumney <jasonr@gnu.org>
>> Subject: Re: Policy issue in the VC manual -- recommending CVS?!?
>> To: "Eric S. Raymond" <esr@snark.thyrsus.com>
>> Cc: emacs-devel@gnu.org
>> Message-ID: <470D40AA.6020400@gnu.org> Content-Type: text/plain;
>> charset=ISO-8859-1
>> 
>> Eric S. Raymond wrote:
>> > Recommending GNU arch is dubious considering Arch's
>> > poorly-maintained and poorly-documented state.  If I'm not
>> > mistaken, Arch has been effectively moribund since about 2003.
>> >   
>> 
>> I think you're mistaken. Savannah lists the last release as July last
>> year.

> So it's only been over a year since the last point release.  I'm not
> hugely reassured.

        I can assure you that the tool is functional, and is in
 production use in a number of projects. 

>> > Recommending CVS is well beyond dubious into outright ridiculous.
>> 
>> Like it or not, CVS is stable, and widely used. Its "problems" are
>> widely exaggerated by adherents to the latest wave of version control
>> religions.

> Er.  I've been using VCSes since the days when SCCS was the only one
> in existence.  The fact that I still cheerfully use RCS, the second
> one ever built, makes me pretty bulletproof against charges of
> version-control faddism.  But file-oriented VCSes just plain suck for
> distributed projects, and there's no way to make them not suck.

>> > No recommendations at all would be better than these.  Who decides
>> > what the manual recommends?  If it's "the last person to care", I'm
>> > going to nuke these in a nanosecond.
>> Arch is part of GNU

> Please tell me you're not implying that we should recommend an
> inferior GPLed tool over a superior one just because the inferior is
> distributed from an FSF server.  That would be taking political
> jaundice to an absurd extreme.

        I think you first have to make your case that arch is
 inferior. It does not change a whole lot, but what we have works just
 fine.  Over the last year I have twice evaluate bzr and git, and found
 that they do not support the feature set of arch that I have come to
 rely upon -- so in my view, at least, bzr and git are the inferior
 products. YMMV.

        manoj
-- 
God isn't dead, he just couldn't find a parking place.
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

  reply	other threads:[~2007-10-10 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071010211743.5104873931@grelber.thyrsus.com>
2007-10-10 21:44 ` Manual policy (Re: Emacs-devel Digest, Vol 44, Issue 65) Eric S. Raymond
2007-10-10 22:00   ` Manoj Srivastava [this message]
2007-10-10 22:07   ` Jason Rumney
2007-10-10 22:55     ` Eric S. Raymond
2007-10-12 18:09       ` Stephen J. Turnbull
2007-10-11 14:46   ` Stefan Monnier
2007-10-11 15:03     ` Eric S. Raymond
2007-10-11 15:05       ` David Kastrup

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=87641e4om7.fsf@anzu.internal.golden-gryphon.com \
    --to=srivasta@ieee.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.