From: "Fiodar Stryzhniou via gdb" <gdb@sourceware.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Petr Ovtchenkov <ptr@void-ptr.info>,
binutils@sourceware.org, Joel Brobecker <brobecker@adacore.com>,
Matthias Klose <doko@ubuntu.com>,
gdb@sourceware.org
Subject: RE: meaning of "Automatic date update in version.in" commits
Date: Thu, 21 Sep 2017 05:03:00 -0000 [thread overview]
Message-ID: <yyRSFRMK2lz0.xJ9T1cbZ@smtp.mail.ru> (raw)
I propose set date with git hook. With every commit create bfd/version.in before commit and vice versa.
Fiodar Stryzhniou
исходное сбщ
Тема: Re: meaning of "Automatic date update in version.in" commits
От: Andreas Schwab <schwab@linux-m68k.org>
Дата: 21.09.2017 00.35
On Sep 20 2017, Petr Ovtchenkov <ptr@void-ptr.info> wrote:
> You see:
>
> git show 3110f4be18a2
> commit 3110f4be18a2f3b9fcd9663ed1dd141bbd6ed14f
> Author: GDB Administrator <gdbadmin@sourceware.org>
> Date: Wed Sep 20 00:01:01 2017 +0000
>
> Automatic date update in version.in
>
> diff --git a/bfd/version.h b/bfd/version.h
> index 3405e42..955269f 100644
> --- a/bfd/version.h
> +++ b/bfd/version.h
> @@ -1,4 +1,4 @@
> -#define BFD_VERSION_DATE 20170919
> +#define BFD_VERSION_DATE 20170920
> #define BFD_VERSION @bfd_version@
> #define BFD_VERSION_STRING @bfd_version_package@ @bfd_version_string@
> #define REPORT_BUGS_TO @report_bugs_to@
>
> git show f625a739
> commit f625a739e567f0110b2675539b7a0e5d5f67c5dc
> Author: GDB Administrator <gdbadmin@sourceware.org>
> Date: Wed Sep 20 00:01:22 2017 +0000
>
> Automatic date update in version.in
>
> diff --git a/bfd/version.h b/bfd/version.h
> index 3405e42..955269f 100644
> --- a/bfd/version.h
> +++ b/bfd/version.h
> @@ -1,4 +1,4 @@
> -#define BFD_VERSION_DATE 20170919
> +#define BFD_VERSION_DATE 20170920
> #define BFD_VERSION @bfd_version@
> #define BFD_VERSION_STRING @bfd_version_package@ @bfd_version_string@
> #define REPORT_BUGS_TO @report_bugs_to@
>
> git diff 3110f4be18a2 f625a739
> ...
> Ooops....
>
> This approch produce ambiguity, but try to conceal it.
You look at two different snapshots. What do you expect?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2017-09-21 5:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 5:03 Fiodar Stryzhniou via gdb [this message]
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
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=yyRSFRMK2lz0.xJ9T1cbZ@smtp.mail.ru \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=doko@ubuntu.com \
--cc=fedor_qd@mail.ru \
--cc=ptr@void-ptr.info \
--cc=schwab@linux-m68k.org \
/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