git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>,
	Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH v2 1/1] t6042: work around speed optimization on Windows
Date: Thu, 17 Jan 2019 12:57:44 -0800	[thread overview]
Message-ID: <xmqqo98fm27r.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <55b0a641d4cd3af37806300e10be36925716e86b.1547713759.git.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Thu, 17 Jan 2019 00:29:21 -0800 (PST)")

"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:

> From: Johannes Schindelin <johannes.schindelin@gmx.de>
>
> When Git determines whether a file has changed, it looks at the mtime,
> at the file size, ...
> Functionally, we do not change anything because we replace two `git mv
> <old> <new>` calls (where `<new>` is completely overwritten and `git
> add`ed later anyway) by `git rm <old>` calls (removing other files, too,
> that are also completely overwritten and `git add`ed later).

Thanks, both.  Will queue.

      reply	other threads:[~2019-01-17 20:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 13:37 [PATCH 0/1] t6042: fix breakage on Windows Johannes Schindelin via GitGitGadget
2019-01-16 13:37 ` [PATCH 1/1] t6042: work around speed optimization " Johannes Schindelin via GitGitGadget
2019-01-16 15:56   ` Elijah Newren
2019-01-16 20:30     ` Johannes Schindelin
2019-01-16 21:13       ` Elijah Newren
2019-01-17  9:35         ` Johannes Schindelin
2019-01-16 15:32 ` [PATCH 0/1] t6042: fix breakage " Elijah Newren
2019-01-16 20:41   ` Johannes Schindelin
2019-01-17  8:29 ` [PATCH v2 " Johannes Schindelin via GitGitGadget
2019-01-17  8:29   ` [PATCH v2 1/1] t6042: work around speed optimization " Johannes Schindelin via GitGitGadget
2019-01-17 20:57     ` Junio C Hamano [this message]

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=xmqqo98fm27r.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=newren@gmail.com \
    /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).