hugin-devs team mailing list archive

Thread
Date

[Bug 685876] Re: Version number reporting

To: hugin-devs@xxxxxxxxxxxxxxxxxxx
From: Yuv <685876@xxxxxxxxxxxxxxxxxx>
Date: Sun, 26 Dec 2010 19:14:26 -0000
Reply-to: Bug 685876 <685876@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: enblend
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685876

Title:
  Version number reporting

Status in Enblend:
  Fix Released

Bug description:
  with -V enblend and enfuse from the repository report version 3.2-cvs

this is too unprecise to understand bug reports. I very much prefer the version number as set in Christoph Spiel's staging branch, e.g.

3.2-staging-rev335

the revision helps a lot, much more than the (deprecated) CVS indication. Of course for stable releases only 3.2 suffice.

also it would be nice to add the version number to the help file that appears when starting enblend / enfuse without parameters. At the _end_ of the help text, please.