Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Frank Schmitt <ich@frank-schmitt.net>
Subject: Re: cvs keyword hacking in texi/Makefile.in
Date: Thu, 24 Mar 2005 14:33:17 +0100	[thread overview]
Message-ID: <v9br99dv8i.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <buo4qf15r9z.fsf@mctpc71.ucom.lsi.nec.co.jp>

On Thu, Mar 24 2005, Miles Bader wrote:

>    # FIXME: This should be done in xml2texi.scm or gnus-faq.xml should be
>    # changed:
>            sed '/\$$Id: Makefile.in,v 7.12 2005/03/24 09:14:37 miles Exp $$/d' < $@.tmp > $@
>
> Besides the more general question of whether CVS keywords should be
> used at all, this probably doesn't do what someone thought it does
> -- it replaces the expansion of $Id$ for `Makefile.in' in the text
> of `gnus-faq.xml'?!?  That's surely a nop...?

Oops, it was supposed to remove the gnus-faq.xml-Id when creating
gnus-faq.texi.  Of course it worked fine, until I committed it.  :-/

Unless Frank or Karl come up with a better idea (see the Makefile
comment above), I will probably the CVS keyword from gnus-faq.xml.

A different approach would be to do the following in Makefile.in...
|  sed '/[$$]Id:.*[$$]/d' < $@.tmp > $@
... which will give...
|  sed '/[$]Id:.*[$]/d' < gnus-faq.texi.tmp > gnus-faq.texi
... on the shell.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2005-03-24 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24  9:26 Miles Bader
2005-03-24 13:33 ` Reiner Steib [this message]
2005-03-24 22:27   ` Karl Pflästerer
2005-03-25  1:48     ` Miles Bader
2005-03-25 10:32       ` Reiner Steib
2005-03-25 12:42         ` Karl Pflästerer

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=v9br99dv8i.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ich@frank-schmitt.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).