all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Tip: restoring your CVS access to savannah
Date: Tue, 20 Dec 2005 22:29:34 +0200	[thread overview]
Message-ID: <uwthzeclt.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1051220075948.371A-100000@acm.acm> (message from Alan Mackenzie on Tue, 20 Dec 2005 08:11:00 +0000 (GMT))

> Date: Tue, 20 Dec 2005 08:11:00 +0000 (GMT)
> From: Alan Mackenzie <acm@muc.de>
> cc: emacs-devel@gnu.org
> 
> >>     acmacm@cvs.savannah.gnu.org:/cvsroot/emacs
> >> 
> >>            ^^^^
> 
> >Yeah, and then get used to the gobbledygook it prints on every
> >commit...
> 
> You mean,
> 
>     cvs commit: Using deprecated info format strings.  Convert your scripts to
>     use the new argument format and remove '1's from your info file format
>     strings.
> 
> ?

Yes.

> Does "info" mean info, as in info pages?  Probably not.  But it's
> something that's got "format strings" of one kind or another.  I
> wonder what "scripts" are meant, because I didn't use any, having
> merely typed "cvs commit programs.texi".

The scripts in question are scripts used by the CVS server on
savannah, the page that you cited explains that.  The savannah
maintainers said simply to disregard these messages, as they will go
away when they (the maintainers) fix those scripts at some later date.

  reply	other threads:[~2005-12-20 20:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 21:16 Tip: restoring your CVS access to savannah Alan Mackenzie
2005-12-19 22:41 ` Eli Zaretskii
2005-12-20  8:11   ` Alan Mackenzie
2005-12-20 20:29     ` Eli Zaretskii [this message]
2005-12-20 22:04       ` Stefan Monnier
2006-01-09 18:31         ` Derek R. Price
2005-12-20 21:47     ` Juri Linkov

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=uwthzeclt.fsf@gnu.org \
    --to=eliz@gnu.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.