From: Jens Remus via Gdb <gdb@sourceware.org>
To: Alan Modra <amodra@gmail.com>, Paul Koning <paulkoning@comcast.net>
Cc: Joel Brobecker <brobecker@adacore.com>,
Tom Tromey <tromey@adacore.com>, Sam James <sam@gentoo.org>,
binutils@sourceware.org, gdb@sourceware.org,
rostiprodev@gmail.com
Subject: Re: On automated commits
Date: Thu, 27 Jun 2024 18:06:43 +0200 [thread overview]
Message-ID: <0e781109-d850-4e27-9c2a-0377dc266179@linux.ibm.com> (raw)
In-Reply-To: <Zn1shv8GuZr2FIW0@squeak.grove.modra.org>
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
jremus@de.ibm.com
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/
next prev parent reply other threads:[~2024-06-27 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 23:17 Sam James via Gdb
2024-06-25 6:15 ` Jan Beulich via Gdb
2024-06-26 17:41 ` Tom Tromey via Gdb
2024-06-26 18:08 ` Fangrui Song
2024-06-26 18:17 ` Joel Brobecker via Gdb
2024-06-27 1:32 ` Alan Modra via Gdb
2024-06-27 2:46 ` H.J. Lu via Gdb
2024-06-27 3:04 ` Jiang, Haochen via Gdb
2024-06-27 3:06 ` Sam James via Gdb
2024-06-27 13:23 ` Paul Koning via Gdb
2024-06-27 13:43 ` Alan Modra via Gdb
2024-06-27 16:06 ` Jens Remus via Gdb [this message]
2024-07-02 14:59 ` John Baldwin via Gdb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e781109-d850-4e27-9c2a-0377dc266179@linux.ibm.com \
--to=gdb@sourceware.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=jremus@linux.ibm.com \
--cc=paulkoning@comcast.net \
--cc=rostiprodev@gmail.com \
--cc=sam@gentoo.org \
--cc=tromey@adacore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox