From: "H.J. Lu" <hjl.tools@gmail.com>
To: binutils@sourceware.org,Andreas Schwab
<schwab@linux-m68k.org>,Petr Ovtchenkov <ptr@void-ptr.info>
Cc: Alan Modra <amodra@gmail.com>,Joel Brobecker
<brobecker@adacore.com>,Matthias Klose <doko@ubuntu.com>,Simon
Marchi <simon.marchi@polymtl.ca>,Pedro Alves
<palves@redhat.com>,Matt Rice <ratmice@gmail.com>,Fiodar
Stryzhniou <fedor_qd@mail.ru>,Binutils
<binutils@sourceware.org>,GDB <gdb@sourceware.org>
Subject: Re: meaning of "Automatic date update in version.in" commits
Date: Fri, 22 Sep 2017 22:35:00 -0000 [thread overview]
Message-ID: <7F438DCC-E2AC-45A1-86CB-71A1C01E89FA@gmail.com> (raw)
In-Reply-To: <87y3p7fcsk.fsf@linux-m68k.org>
On September 22, 2017 2:49:31 PM GMT+08:00, Andreas Schwab <schwab@linux-m68k.org> wrote:
>On Sep 22 2017, Petr Ovtchenkov <ptr@void-ptr.info> wrote:
>
>> I.e. development process of kernel or glibc (ABI is important and
>"source
>> identification" important too, isn't it?) dispense of such technique,
>
>Unlike kernel and glibc, libbfd and libopcodes do not maintain ABI
>compatibility, and never will.
>
>> but binutils prefer to follow tradition from 1994 that was useful
>> for publicly inaccessible CVS repo + public tarball on FTP.
>
>bfd/version.h has been added in 2001, not 1994. It still works very
>well, no need to change anything that isn't broken.
>
>Andreas.
We should try not to update DATE in version.h if there is no change
otherwise. It can be done by remembering the last commit.
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2017-09-22 22:35 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 5:03 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 [this message]
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
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
[not found] <20170920173622.28500ccf@void-ptr.info>
2017-09-20 15:05 ` Joel Brobecker
2017-09-20 15:33 ` Petr Ovtchenkov
2017-09-21 17:07 ` Ian Lance Taylor via gdb
2017-09-20 15:40 ` Matthias Klose
2017-09-20 15:48 ` Dmitry Samersoff
[not found] ` <87zi9p2vma.fsf@linux-m68k.org>
2017-09-20 17:24 ` Petr Ovtchenkov
[not found] ` <7217d33d-61eb-732e-dfd6-80ef4908743e@ubuntu.com>
2017-09-20 19:21 ` Petr Ovtchenkov
2017-09-20 19:27 ` Mikhail Terekhov
2017-09-20 19:56 ` Philippe Waroquiers
2017-09-20 19:57 ` Matthias Klose
2017-09-20 20:07 ` Philippe Waroquiers
2017-09-20 20:21 ` Matthias Klose
2017-09-20 20:26 ` Philippe Waroquiers
2017-09-20 20:31 ` Petr Ovtchenkov
2017-09-20 20:39 ` Philippe Waroquiers
2017-09-20 20:34 ` Mikhail Terekhov
2017-09-20 21:34 ` Andreas Schwab
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=7F438DCC-E2AC-45A1-86CB-71A1C01E89FA@gmail.com \
--to=hjl.tools@gmail.com \
--cc=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