On Thursday, May 01, 2014 03:14:42 PM Jan Engelhardt wrote:
> On Thursday 2014-05-01 15:04, Paul Moore wrote:
> >> >For the master branch the version has always been kept at 0.0.0 to help
> >> >make it obvious that this is not a real release. The version number
> >> >will
> >> >be changed to something useful for releases.
> >>
> >> I see. However, if the commit+tag that changes it from 2.1.0 to 0.0.0
> >> will
> >> not end up on master (like it was done for v2.0.0), then `git describe`
> >> becomes useless.
> >
> >In the past I typically branch master then change from 0.0.0 to the release
> >version. Does that work for you?
>
> What I mean is that the git tag should not be on {a branch that will
> never get back into master}.
Why not? I ask this never having used 'git describe'.
--
paul moore
security and virtualization @ redhat
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
libseccomp-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libseccomp-discuss
