From: Alan Modra <amodra@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Petr Ovtchenkov <ptr@void-ptr.info>,
Joel Brobecker <brobecker@adacore.com>,
Matthias Klose <doko@ubuntu.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
Matt Rice <ratmice@gmail.com>,
Fiodar Stryzhniou <fedor_qd@mail.ru>,
Andreas Schwab <schwab@linux-m68k.org>,
Binutils <binutils@sourceware.org>, GDB <gdb@sourceware.org>
Subject: Re: [PATCH] bfd/version.h: Add rationale for BFD_VERSION_DATE (Re: meaning of "Automatic date update in version.in" commits)
Date: Fri, 22 Sep 2017 13:38:00 -0000 [thread overview]
Message-ID: <20170922133806.GH25070@bubble.grove.modra.org> (raw)
In-Reply-To: <0f7c205c-7ecb-bc49-bf15-c753e576cdc0@redhat.com>
On Fri, Sep 22, 2017 at 10:49:05AM +0100, Pedro Alves wrote:
> I like this summary. How about we put something like that in bfd/version.h ?
Good idea.
> I assume that the bot is just replacing the line with
> BFD_VERSION_DATE instead of regenerating the whole file from
> scratch, but that's just guessing. (I don't have sourceware
> shell access; I have no idea how the auto updater is implemented.)
Back when I ran the cron job on my home machine, it did
sed -e 's/20[0-9]*/'`date +%Y%m%d`/ < bfd/version.h > bfd/version.h.new
I'm not sure what is done nowadays. You could always commit the patch
and see what happens. :)
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2017-09-22 13:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 5:03 meaning of "Automatic date update in version.in" commits Fiodar Stryzhniou via gdb
2017-09-21 8:42 ` Matt Rice
2017-09-21 10:58 ` Petr Ovtchenkov
2017-09-21 11:37 ` Pedro Alves
[not found] ` <20170921152240.16bb4cc0@void-ptr.info>
2017-09-21 12:39 ` Pedro Alves
2017-09-21 13:17 ` Petr Ovtchenkov
2017-09-21 13:34 ` Simon Marchi
2017-09-21 15:46 ` Petr Ovtchenkov
2017-09-21 16:01 ` Simon Marchi
2017-09-21 16:03 ` Matthias Klose
2017-09-21 16:26 ` Petr Ovtchenkov
2017-09-21 16:34 ` Joel Brobecker
2017-09-21 16:52 ` Petr Ovtchenkov
2017-09-21 17:00 ` Joel Brobecker
2017-09-21 17:39 ` Petr Ovtchenkov
2017-09-21 23:59 ` Alan Modra
2017-09-22 5:31 ` Petr Ovtchenkov
2017-09-22 6:49 ` Andreas Schwab
2017-09-22 9:29 ` Petr Ovtchenkov
2017-09-22 22:26 ` H.J. Lu
2017-09-22 22:35 ` H.J. Lu
2017-09-22 9:49 ` [PATCH] bfd/version.h: Add rationale for BFD_VERSION_DATE (Re: meaning of "Automatic date update in version.in" commits) Pedro Alves
2017-09-22 13:38 ` Alan Modra [this message]
2017-09-22 13:47 ` Joel Brobecker
2017-09-22 13:59 ` Pedro Alves
2017-09-21 17:17 ` meaning of "Automatic date update in version.in" commits Joseph Myers
2017-09-21 17:31 ` Matt Rice
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=20170922133806.GH25070@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=doko@ubuntu.com \
--cc=fedor_qd@mail.ru \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=ptr@void-ptr.info \
--cc=ratmice@gmail.com \
--cc=schwab@linux-m68k.org \
--cc=simon.marchi@polymtl.ca \
/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