From: Andreas Schwab <schwab@suse.de>
To: Pedro Alves <palves@redhat.com>
Cc: Kamil Rytarowski <n54@gmx.com>,
gdb@sourceware.org,
Sergio Durigan Junior <sergiodj@sergiodj.net>
Subject: Re: gettext.m4 update
Date: Wed, 13 Sep 2017 13:21:00 -0000 [thread overview]
Message-ID: <mvmlgliag4q.fsf@suse.de> (raw)
In-Reply-To: <9c14709c-0f65-b2c4-9b7e-a1cac8346f98@redhat.com> (Pedro Alves's message of "Wed, 13 Sep 2017 14:14:54 +0100")
On Sep 13 2017, Pedro Alves <palves@redhat.com> wrote:
> Maybe the bot should be doing a recursive touch(1) of all files
> after checkout, forcing the same mtime on all checked-out files,
> with 'touch -d ..' or 'touch -p ..' or
> 'touch -r .git/FETCH_HEAD' or something like that.
Or touch each file to the ctime of the last commit that modified it.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2017-09-13 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 13:34 Kamil Rytarowski
2017-09-13 11:53 ` Kamil Rytarowski
2017-09-13 13:15 ` Pedro Alves
2017-09-13 13:21 ` Andreas Schwab [this message]
2017-09-13 13:37 ` Kamil Rytarowski
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=mvmlgliag4q.fsf@suse.de \
--to=schwab@suse.de \
--cc=gdb@sourceware.org \
--cc=n54@gmx.com \
--cc=palves@redhat.com \
--cc=sergiodj@sergiodj.net \
/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