Date: Thu, 24 Dec 2020 10:28:06 -0500 From: grarpamp <grarpamp@gmail.com> To: freebsd-current@freebsd.org Subject: Re: git and the loss of revision numbers Message-ID: <CAD2Ti28WcausXAtnxAcCpkfz8qqNLoQn_RLWDkiYBZMFTU8BHA@mail.gmail.com> In-Reply-To: <54116640-E6A1-4C53-9D7E-4384F942628E@ellael.org> References: <54116640-E6A1-4C53-9D7E-4384F942628E@ellael.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> loss of continuously increasing revision numbers git rev-list --count HEAD git describe --tags / parent Plus a bunch of similar ways to do it, from different points, in different formats, search internet for them all... git revision version numbering... Some deploy structured metadata in tag schemes, use hooks, files, etc but gets messy and is not just a simple proper read-only query. > date of the commit besides its hash being reported > whether to recompile Recompilation means users have the source cloned. Source means users can use ways like git log <hash> git show etc Which means users have date, and a <hash> in log subsequent to their last compiled hash etc. So it's not a problem beyond a few trivial steps or shell parsing function to query and compare on whatever particular metadata a person may like, to what they already know they have. The handbook will have docs on some ways.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti28WcausXAtnxAcCpkfz8qqNLoQn_RLWDkiYBZMFTU8BHA>