From: Peter Backes <rtc@helen.PLASMA.Xg8.DE>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Git should preserve modification times at least on request
Date: Mon, 19 Feb 2018 23:08:19 +0100 [thread overview]
Message-ID: <20180219220819.GA10466@helen.PLASMA.Xg8.DE> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1802192257100.31@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>
Hi Johannes,
On Mon, Feb 19, 2018 at 10:58:12PM +0100, Johannes Schindelin wrote:
> Since you already assessed that it shouldn't be hard to do, you probably
> want to put your money where your mouth is and come up with a patch, and
> then offer it up for discussion on this here mailing list.
Well, it would be good to discuss this a bit beforehand, since my time
is wasted if there's no chance to get it accepted. Perhaps there is
some counterargument I don't know about.
Is there some existing code that could be used? I think I read
somewhere that git once did preserve mtimes, but that this code was
removed because of the build tool issues. Perhaps that code could
simply be put back in, and surrounded by conditions.
Best wishes
Peter
PS: Given the opportunity, I want to thank you very much for
maintaining the git repository for my cvsclone tool.
--
Peter Backes, rtc@helen.PLASMA.Xg8.DE
next prev parent reply other threads:[~2018-02-19 22:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 21:22 Git should preserve modification times at least on request Peter Backes
2018-02-19 21:58 ` Johannes Schindelin
2018-02-19 22:08 ` Peter Backes [this message]
2018-02-20 1:22 ` Theodore Ts'o
2018-02-20 10:46 ` Johannes Schindelin
2018-02-20 11:53 ` Peter Backes
2018-02-20 21:05 ` Peter Backes
2018-02-20 22:32 ` Johannes Schindelin
2018-02-20 22:48 ` Peter Backes
2018-02-21 21:30 ` Phillip Wood
2018-02-19 22:37 ` Randall S. Becker
2018-02-19 23:22 ` Hilco Wijbenga
2018-02-20 16:42 ` Hilco Wijbenga
2018-02-20 21:16 ` Jeff King
2018-02-20 22:05 ` Peter Backes
2018-02-21 9:48 ` Jacob Keller
2018-02-20 23:40 ` Junio C Hamano
2018-02-21 21:03 ` Derek Fawcus
2018-02-21 21:33 ` Ævar Arnfjörð Bjarmason
2018-02-21 22:14 ` Peter Backes
2018-02-21 22:44 ` Ævar Arnfjörð Bjarmason
2018-02-21 23:12 ` Peter Backes
2018-02-21 23:58 ` Randall S. Becker
2018-02-22 2:05 ` 'Peter Backes'
2018-02-26 10:56 ` Andreas Krey
2018-02-26 11:04 ` 'Peter Backes'
2018-02-22 23:24 ` Derek Fawcus
2018-02-23 12:28 ` Konstantin Khomoutov
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180219220819.GA10466@helen.PLASMA.Xg8.DE \
--to=rtc@helen.plasma.xg8.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).