Re: GUB problems with git describe

[John Mandereau]

Le mercredi 23 septembre 2009 à 11:50 +0100, Graham Percival a écrit : 
> I can work-around the problem by adding --always to the git describe
> command-line, but then we end up with tags like this:
>   git tag -m "release of lilypond
> 834700852f25a6ade4a2f8efe2b13bc71278d3a (2.13.4-0)"
> "gub-release-lilypond-2.13.4-0"
> 
> 1)  Do we care if the tag comment looks like this?

I dunno, what is it supposed to look like?  The most important is that
it's named release/2.13.4-1 (and not 0).


> 2)  If not, can anybody suggest a better way of fixing the git
> describe command-line?

Yes, use a full Git repository instead of a shallow copy obtained with
"git clone --depth".  Maybe this is not the problem, but I guess it
might be.

HTH,
John

signature.asc
Description: Ceci est une partie de message numériquement signée