From: Fangrui Song <i@maskray.me>
To: Sam James <sam@gentoo.org>, rostiprodev@gmail.com
Cc: Tom Tromey <tromey@adacore.com>,
binutils@sourceware.org, gdb@sourceware.org
Subject: Re: On automated commits
Date: Wed, 26 Jun 2024 11:08:47 -0700 [thread overview]
Message-ID: <DS7PR12MB5765DD21C2534BEDBB592C1CCBD62@DS7PR12MB5765.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87bk3nsisx.fsf@tromey.com>
On Wed, Jun 26, 2024 at 10:41 AM Tom Tromey <tromey@adacore.com> wrote:
>
> Sam> Nick also then says:
> >> I do like the idea of the configure file generating the bfd/version.h file
> >> automatically however, so if someone wants to write a potential patch that
> >> would be great.
>
> Sam> Rostislav on the PR seems he may be up for working on it, but if he
> Sam> can't, I might be able to when I'm less busy.
>
> Sam> Thoughts?
>
> I personally have never liked these automated commits, and I can't
> recall ever using the date they provide.
>
> I also don't believe these dates are used here at AdaCore.
>
> So +1 from me for removing these.
>
> thanks,
> Tom
+1 from me for removing "Automatic date update in version.in" commits.
They are a distraction when investigating the history in the bfd/
directory `git log -- bfd/`.
next prev parent reply other threads:[~2024-06-26 18:16 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 [this message]
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
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=DS7PR12MB5765DD21C2534BEDBB592C1CCBD62@DS7PR12MB5765.namprd12.prod.outlook.com \
--to=i@maskray.me \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--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