Re: On automated commits
Jens Remus <[email protected]>
| Newsgroups | gmane.comp.gnu.binutils,gmane.comp.gdb.devel |
|---|---|
| Organization | IBM Deutschland Research & Development GmbH |
| Message-ID | <[email protected]> |
Am 27.06.2024 um 15:43 schrieb Alan Modra:
> On Thu, Jun 27, 2024 at 09:23:20AM -0400, Paul Koning wrote:
>> So why not have the build procedure pick up the last commit date, if building in a Git sandbox? That's easy enough to arrange. Similarly, it could pick up the identifier (SHA hash) of that last commit to make it entirely unambiguous.
>
> I wasn't saying the way we do things now is the only way, just
> explaining why the date is useful. "git show -s --oneline @{u}" or
> similar would be good too, but let's make sure we report upstream
> commits not local ones.
@{u} refers to the tracking branch. In my setup that is not the upstream
Binutils repository but my personal internal fork.
Regards,
Jens
--
Jens Remus
Linux on Z Development (D3303) and z/VSE Support
+49-7031-16-1128 Office
[email protected]
IBM
IBM Deutschland Research & Development GmbH; Vorsitzender des
Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der
Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM Data Privacy Statement: https://www.ibm.com/privacy/