Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #144276

Re: Tagging programs with git hash. [slightly OT]

Path csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From Keith Thompson <kst-u@mib.org>
Newsgroups comp.lang.c
Subject Re: Tagging programs with git hash. [slightly OT]
Date Sat, 01 Jun 2019 14:34:28 -0700
Organization None to speak of
Lines 30
Message-ID <lnr28douqj.fsf@kst-u.example.com> (permalink)
References <dc2a28eb-b00b-4151-b7de-ede01ab3d373@googlegroups.com> <slrn3s8cqf5r6v.4e6.ike@iceland.freeshell.org>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Injection-Info reader02.eternal-september.org; posting-host="dc11016993605ffbfd13f712ec1a0add"; logging-data="21856"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX180P5hpAKGidTMrUJN4Pt7G"
User-Agent Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock sha1:+Q2DgQb1B18Rq70Yn4s8qzDslrs= sha1:9Yd7uAXh8EMgByMbQbhf5aQJaac=
Xref csiph.com comp.lang.c:144276

Show key headers only | View raw


Ike Naar <ike@iceland.freeshell.org> writes:
> On 2019-05-31, Malcolm McLean <malcolm.arthur.mclean@gmail.com> wrote:
>> Git and similar version control systems have an internal version tag,
>> in git it is the sha-1 hash, which is used to identify the version
>> within the control system.
>>
>> Now it would be nice to tag the executable with this hash, so that if
>> a user reports a bug, you can ask them to run it in a mode that
>> displays the hash, then go back to the correct version in the
>> repository to find the bug.
>
> Why not simply tag it with the version number itself?
> What's the benefit of using a hash?

For example, if I'm developing a program, I'd like to be able to build a
version of it based on what I've just checked in, which likely won't
have a defined version number.  I'm going to be building working (or
non-working) versions of the program much more often than I'm going to
be doing "official" releases.

One alternative is to define a new version number for each commit.  vim
does this; the latest version in its git repo is v8.1.1446.  But if you
don't want to do that, a version that includes the date and (part of)
the git commit hash also works, and uniquely identifies the version of
the source from which it was built.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Tagging programs with git hash. [slightly OT] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-05-31 07:02 -0700
  Re: Tagging programs with git hash. [slightly OT] queequeg@trust.no1 (Queequeg) - 2019-05-31 14:27 +0000
    Re: Tagging programs with git hash. [slightly OT] Mateusz Viste <mateusz@wont.tell> - 2019-05-31 16:42 +0000
      Re: Tagging programs with git hash. [slightly OT] Keith Thompson <kst-u@mib.org> - 2019-05-31 13:23 -0700
      Re: Tagging programs with git hash. [slightly OT] queequeg@trust.no1 (Queequeg) - 2019-05-31 21:10 +0000
        Re: Tagging programs with git hash. [slightly OT] Mateusz Viste <mateusz@wont.tell> - 2019-06-01 09:31 +0000
          Re: Tagging programs with git hash. [slightly OT] queequeg@trust.no1 (Queequeg) - 2019-06-01 12:39 +0000
  Re: Tagging programs with git hash. [slightly OT] David Brown <david.brown@hesbynett.no> - 2019-05-31 16:28 +0200
  Re: Tagging programs with git hash. [slightly OT] fir <profesor.fir@gmail.com> - 2019-05-31 07:51 -0700
  Re: Tagging programs with git hash. [slightly OT] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-05-31 15:59 +0100
    Re: Tagging programs with git hash. [slightly OT] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-05-31 22:56 +0100
      Re: Tagging programs with git hash. [slightly OT] John Forkosh <forkosh@panix.com> - 2019-06-01 02:55 +0000
        Re: Tagging programs with git hash. [slightly OT] fir <profesor.fir@gmail.com> - 2019-06-01 04:26 -0700
          Re: Tagging programs with git hash. [slightly OT] fir <profesor.fir@gmail.com> - 2019-06-01 04:35 -0700
      Re: Tagging programs with git hash. [slightly OT] Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-06-01 04:03 -0700
  Re: Tagging programs with git hash. [slightly OT] "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-05-31 13:30 -0700
  Re: Tagging programs with git hash. [slightly OT] Eli the Bearded <*@eli.users.panix.com> - 2019-05-31 21:46 +0000
  Re: Tagging programs with git hash. [slightly OT] Shuggie <shuggie@latepaul.com> - 2019-06-01 11:21 +0100
  Re: Tagging programs with git hash. [slightly OT] Ike Naar <ike@iceland.freeshell.org> - 2019-06-01 21:23 +0000
    Re: Tagging programs with git hash. [slightly OT] Keith Thompson <kst-u@mib.org> - 2019-06-01 14:34 -0700
    Re: Tagging programs with git hash. [slightly OT] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-06-02 12:36 -0700
      Re: Tagging programs with git hash. [slightly OT] Keith Thompson <kst-u@mib.org> - 2019-06-02 14:35 -0700

csiph-web