Re: Can't get a patch through because of weekly development releases.

[Graham Percival]

On Wed, Jul 14, 2010 at 08:56:25PM +0200, David Kastrup wrote:
> Carl Sorensen <address@hidden> writes:
> 
> > The version number of a build from the current git will be higher than
> > the last release version.  This particular patch uses changes in .cc
> > code, so it needs to be rebuilt, and hence will always be a version
> > ahead of the current git.
> 
> That sounds like the version number for a feature branch should be
> something like
> 2.14.13.feature
> where "x.feature" > "x".

We _could_ do that... VERSION has an entry for such a number, so I
assume that at some point, the build system supported them.  I
don't know if it still does, nor whether convert-ly still does,
etc.

I think that writing a 5-10 line shell script for easily updating
version numbers in a patch/commit would be much less work than
checking all the above, though.

Cheers,
- Graham