Revision information in sources?

[Brian de Alwis]

You might also look at the 'keywords' plugin:

	https://launchpad.net/bzr-keywords

Brian.

On 9-Jun-2011, at 1:07 PM, J. Bobby Lopez wrote:

> I suppose, instead of doing a 'bzr export',  I could just do something like:
> 
> bzr branch <remote_branch> ./new_branch;
> cd new_branch/;
> echo $(bzr tags -r `bzr revno`) > VERSION.txt;
> rm -fr .bzr;
> 
> Was just curious if there was a more common way of doing it.
> 
> 
> On Thu, Jun 9, 2011 at 12:30 PM, J. Bobby Lopez <jbl at jbldata.com> wrote:
> (asked this question on IRC, but realized it may be more suitable to the mailing list)
> 
> Hey all,
> 
> I'm curious what others are doing regarding tags and releases. I'm looking 
> for a way to do a 'bzr export' which also somehow dumps the revision or tag information 
> as part of the export, in order to identify what revision that export came from. I'm 
> not very fond of having to update a hard-coded revision in the sources or readme docs.. 
> but is this what is generally done? Any other elegant ways to manage revision 
> information in an export?
> 
> I realize this question may be similar to "does BZR support CVS-style ID tags". Please chime in if you have suggestions from that point of view as well.
> 
> Thanks,
> -Bobby
>