ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ernesto Schirmacher <ernesto_schirmacher@hotmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Module for svn info
Date: Mon, 21 Jan 2008 22:10:06 -0500	[thread overview]
Message-ID: <BAY128-W13BB02DE8D11846122BD70973E0@phx.gbl> (raw)
In-Reply-To: <4D2077CD-619C-4429-A1D7-733931A9FB5C@csiro.au>


>  If your sources are in svn, then they actually have the same svn- 
> number, after a commit. But the numbers in the $Revision$ or $Id$ tags  
> of your working copies are not updated by svn commit. However, if you  
> do an "svn update" after the commit, it should update the numbers. So,  
> you shouldn't need to work out the maximum value.

The svn keyword Revision or Rev or LastChangedRevision (they are all 
the same) are defined as the last revision where the file changed (see 
subversion book chapter 3 section keyword substitution).  It seems to 
me that subversion does not have a global keyword that would give you
the last revision number.  But they do provide svnversion to get that 
number automatically (see subversion book highlighted box named
"Where's $GlobalRev$?").   So Robin's solution below seems to be the
best way to get the global version number.

> 
>      svnversion> svnversion.tex ; texexec document.tex
> 
> in the Makefile, and on the document front page somewhere
> 
>      \doiffileelse{svnversion.tex}{
>         Subversion revision
>         \ignorespaces \input svnversion\relax \removeunwantedspaces . 
> \crlf
>      }{}
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-01-22  3:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 23:58 Robin Kirkham
2008-01-22  3:10 ` Ernesto Schirmacher [this message]
2008-01-22 11:15   ` Markus Bernhardt
2008-01-23 12:34     ` Aditya Mahajan
     [not found] <mailman.3280.1201040714.4317.ntg-context@ntg.nl>
2008-01-23 11:52 ` Robin Kirkham
2008-01-23 21:26   ` Peter Münster
  -- strict thread matches above, loose matches on Subject: below --
2008-01-20  2:34 Markus Bernhardt
2008-01-20  5:11 ` Aditya Mahajan
2008-01-21  8:32   ` Markus Bernhardt

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=BAY128-W13BB02DE8D11846122BD70973E0@phx.gbl \
    --to=ernesto_schirmacher@hotmail.com \
    --cc=ntg-context@ntg.nl \
    /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).