all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: Option to customize the -m message flag of cvs?
Date: Tue, 6 Jan 2009 22:24:21 +0100	[thread overview]
Message-ID: <f7ccd24b0901061324r6c642dbdn9cfe2ac02b0733de@mail.gmail.com> (raw)
In-Reply-To: <ubpukkuht.fsf@gnu.org>

On Tue, Jan 6, 2009, Eli Zaretskii <eliz@gnu.org> wrote:

> That they use the official port from ftp.gnu.org.

That's unrealistic. They could be using CVSNT because of its many
features over standard CVS.

Moreover, switching from CVSNT to CVS is not necessarily trivial. For
my setup, for example, I would have to checkout Emacs again or modify
every single CVS/root file, which currently is like

   :ssh;key='\path\to\my\key':username@cvs.savannah.gnu.org:/cvsroot/emacs

> It's still an annoyance, and being straightforward about it doesn't
> make it less so.

I can not deny that it is annoying. But I don't think we should be
judging free software as less worthy of our support because of some
minor annoyance.

> I'm suggesting to fix VC instead
> so that the official gnu.org ports could be used instead.

I'm trying CVS 1.12.13a from http://ftp.gnu.org/non-gnu/cvs/binary/,
and, in a ironic twist, that's part of the output of cvs -H:

  The Concurrent Versions System (CVS) is a tool for version control.
  For CVS updates and additional information, see
      the CVS home page at http://www.nongnu.org/cvs/ or
      the CVSNT home page at http://www.cvsnt.org/

    Juanma




  reply	other threads:[~2009-01-06 21:24 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 12:58 Option to customize the -m message flag of cvs? Juanma Barranquero
2008-12-29 17:10 ` martin rudalics
2008-12-29 19:14   ` Eli Zaretskii
2008-12-29 19:57     ` Juanma Barranquero
2008-12-29 20:52       ` Eli Zaretskii
2008-12-29 21:18         ` martin rudalics
2008-12-30  4:04           ` Eli Zaretskii
2008-12-30  7:26             ` martin rudalics
2008-12-30 22:05               ` Eli Zaretskii
2008-12-31  9:15                 ` martin rudalics
2008-12-31 19:14                   ` Eli Zaretskii
2008-12-31 21:28                     ` martin rudalics
2009-01-06 10:57                     ` martin rudalics
2009-01-06 16:08                       ` Dan Nicolaescu
2009-01-06 17:06                         ` Juanma Barranquero
2009-01-06 20:49                           ` Eli Zaretskii
2009-01-06 20:59                             ` Juanma Barranquero
2009-01-06 21:10                               ` Eli Zaretskii
2009-01-07  8:18                             ` martin rudalics
2009-01-07 21:21                               ` Eli Zaretskii
2009-01-06 18:26                         ` Stefan Monnier
2009-01-06 20:21                           ` Juanma Barranquero
2009-01-12 22:18                           ` Sam Steingold
2009-01-12 23:52                             ` Juanma Barranquero
2009-01-13  1:57                               ` dhruva
2009-01-13  1:59                                 ` dhruva
2009-01-13 18:51                               ` Sam Steingold
2009-01-13 21:20                                 ` Juanma Barranquero
2009-01-06 22:32                         ` mail
2009-01-07  8:52                           ` Juanma Barranquero
2009-01-06 20:46                       ` Eli Zaretskii
2009-01-06 20:53                         ` Juanma Barranquero
2009-01-06 21:01                           ` Eli Zaretskii
2009-01-06 21:06                             ` Juanma Barranquero
2009-01-06 21:14                               ` Eli Zaretskii
2009-01-06 21:24                                 ` Juanma Barranquero [this message]
2009-01-06 21:35                           ` Stefan Monnier
2008-12-29 23:29         ` Juanma Barranquero
2008-12-30  9:34         ` Juanma Barranquero

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=f7ccd24b0901061324r6c642dbdn9cfe2ac02b0733de@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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.