unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: Feature freeze and Tramp?
Date: Sat, 08 May 2004 12:15:59 +0200	[thread overview]
Message-ID: <87ad0j5in4.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: 87u0yrvpvk.fsf@tc-1-100.kawasaki.gol.ne.jp

Miles Bader <miles@gnu.org> writes:

> Kai Grossjohann <kai@emptydomain.de> writes:
>> Thanks to everyone for sharing their opinion.  I've now tried to
>> update Tramp to 2.0.40.
>
> The arch tagline for `man/trampver.texi' got stomped on.

Argh.  I forgot, /again/.  Sorry.  I've now tried to resurrect the
line.

> Looking at it, it looks like a generated file -- should it not be stored
> in the archive at all?  Or is a `generated but not locally' file?
> If that's the case I can use an explicit tag instead of a tagline.

In the Tramp CVS repository, the Tramp version is an Autoconf macro.
The file texi/trampver.texi.in in that repository contains an @FOO@
string, and texi/trampver.texi is generated from it to contain the
version number.

Then the file texi/trampver.texi is transferred to the Emacs CVS
repository.

So if I understand you correctly, the `generated but not locally' part
is true.

I've now put the arch tagline in trampver.texi.in, was this the right
thing to do?

Thanks for your patience,
Kai

  reply	other threads:[~2004-05-08 10:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02 18:43 Feature freeze and Tramp? Kai Grossjohann
2004-05-02 19:19 ` David Kastrup
2004-05-03  6:20   ` Eli Zaretskii
2004-05-03  6:03 ` Kim F. Storm
2004-05-03 14:03 ` Richard Stallman
2004-05-07 21:23 ` Kai Grossjohann
2004-05-07 22:22   ` Miles Bader
2004-05-08 10:15     ` Kai Grossjohann [this message]
2004-05-10  1:33       ` Miles Bader
2004-05-10  1:39       ` Miles Bader
2004-05-08  2:34   ` Luc Teirlinck
2004-05-08 10:34     ` Kai Grossjohann
2004-05-09  1:40       ` Luc Teirlinck
2004-05-10 13:02         ` Kai Grossjohann
2004-05-11  2:49           ` Luc Teirlinck
2004-05-11  7:08             ` Kai Grossjohann
2004-05-12  0:53               ` Luc Teirlinck
2004-05-12  1:02               ` Luc Teirlinck
2004-05-12  7:32                 ` Kai Grossjohann
2004-05-12 14:57                   ` Luc Teirlinck
2004-05-13  6:54                     ` Kai Grossjohann
2004-05-13 14:02                       ` Luc Teirlinck
2004-05-15 16:36                         ` Kai Grossjohann
2004-05-15 18:28                           ` Luc Teirlinck
2004-05-16  9:07                             ` Kai Grossjohann
2004-05-17  0:50                               ` Luc Teirlinck
2004-05-17  5:11                                 ` Kai Grossjohann
2004-05-08  3:15   ` Luc Teirlinck
2004-05-09  2:11   ` Luc Teirlinck
2004-05-09 15:35     ` Robert J. Chassell
2004-05-09 16:26       ` Luc Teirlinck
2004-05-09 20:11         ` Stefan Monnier
2004-05-10  0:08           ` Luc Teirlinck
2004-05-09  2:34   ` Luc Teirlinck
2004-05-09  2:53     ` Luc Teirlinck

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ad0j5in4.fsf@emptyhost.emptydomain.de \
    --to=kai@emptydomain.de \
    /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 public inbox

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

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).