From: Phillip Wood <phillip.wood@talktalk.net>
To: Peter Backes <rtc@helen.PLASMA.Xg8.DE>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Git should preserve modification times at least on request
Date: Wed, 21 Feb 2018 21:30:50 +0000 [thread overview]
Message-ID: <0a9f7d75-b362-bb9d-48ef-c4a6a921ff96@talktalk.net> (raw)
In-Reply-To: <20180220224808.GA25678@helen.PLASMA.Xg8.DE>
On 20/02/18 22:48, Peter Backes wrote:
>
> On Tue, Feb 20, 2018 at 11:32:23PM +0100, Johannes Schindelin wrote:
>> Hi Peter,
>>
>> On Tue, 20 Feb 2018, Peter Backes wrote:
>>
>>> On Tue, Feb 20, 2018 at 11:46:38AM +0100, Johannes Schindelin wrote:
>>>
>>>> I would probably invent a file format (`<mtime><TAB><path><LF>`)
>>>
>>> I'm stuck there because of <path> being munged.
>>
>> From which command do you want to get it? If you are looking at `git
>> diff`, you may want to use the `-z --name-only` options to avoid munging
>> the paths.
>
> I plan to use "git diff-tree --name-only $w_tree HEAD" and subtract
> all lines from "git diff-index --name-only HEAD" to get the files for
> which the timestamp should be stored..
>
> If I use "-z" I get the non-munged path, but I cannot safely store such
> paths in the proposed file format; they might contain newlines (sigh).
> So at one point I have to munge. Then the same question arises when I
> have to get the actual path from the munged path when restoring the
> timestamps.
>
> If there's no ready-made functionality to munge and unmunge paths, I
> have to write some awk for this. At first I thought this might add one
> more dependency to git, but it seems that awk is already used in
> git-mergetool.sh, so I suppose it's okay to use in git-stash.sh etc,
> too.
In recent versions of git there's unquote_path() in Git.pm, you could
possibly use that with perl -e from your script
Best Wishes
Phillip
> Best wishes
> Peter
>
next prev parent reply other threads:[~2018-02-21 21:30 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0a9f7d75-b362-bb9d-48ef-c4a6a921ff96@talktalk.net \
--to=phillip.wood@talktalk.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
--cc=rtc@helen.PLASMA.Xg8.DE \
/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;
as well as URLs for NNTP newsgroup(s).