On Mon, Apr 20, 2009 at 9:17 PM, Michael Cronenworth <m...@cchtml.com> wrote: > -------- Original Message -------- > Subject: Re: [Ekiga-devel-list] ekiga.rc > From: Michael Rickmann <mric...@gwdg.de> > To: Ekiga development mailing list <ekiga-devel-list@gnome.org> > Date: 04/20/2009 11:54 AM > >> >> Yes, I have seen that. I am still testing. Would something like >> #define EKIGA_REVISION "EKIGA_3_2_0-80-g80bf6d3" be acceptable in >> revisioin.h? It is based on the output of git describe, the 80th >> revision of tag EKIGA_3_2_0 I guess. > > > You cannot do this. Git does not use revision numbers. It uses a commit > *hash* for tracking. Don't rely on Git hashes. Define another version number > and use that.
Its not (at least in fedora) used as a version number, but rather as a tracking bit in builds that aren't final releases to allow tracking of the exact revision. Peter _______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list