[PATCH 0 of 5] Build on latesttag for archival and mercurial builds

[Gilles Moris]

On Saturday 10 October 2009 12:34:19 am Martin Geisler wrote:
> > Here is an array summarizing the mercurial version string:
> >       [A]       [B]   [C]           [D]
> > [1] archive    tag   clean => tag
> > [2] archive    hash  clean => sha1hash [latesttag+latesttagdistance]
> > [3] archive    tag   dirty => N/A
> > [4] archive    hash  dirty => N/A
> > [5] clone      tag   clean => tag
> > [6] clone      hash  clean => sha1hash [latesttag+latesttagdistance]
> > [7] clone      tag   dirty => tag+date
> > [8] clone      hash  dirty => sha1hash+date
>
> Excellent idea with such a table! Am I correct in thinking that the only
> new behavior is row 2 and 6? I think this looks very reasonable and I
> would like to see us use this scheme.
>

Yes, 2 and 6, but also 7, because the date was not set in that case (Patch 2)

> I'll be traveling to Berlin from Sunday to Wednesday and I wont review
> the patches until I'm back. So if they have not been pushed when I
> return, I'll have a look then -- I hope we can make it in time for the
> feature freeze.

I have people at home this week-end, so I would not have much time to
discuss this series.

I've went to Berlin this summer. This is really a wonderful place. Enjoy!

Regards.
Gilles.