git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Morales Vega <christian.morales.vega@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: git checkout behaviour when only ctime of file changes
Date: Mon, 19 Apr 2021 12:23:14 +0100	[thread overview]
Message-ID: <CAOWQn3Qa68aWH8ztGAej=ctJDw4dkzuPQkkqo6Ydvn=13hV1vw@mail.gmail.com> (raw)
In-Reply-To: <a6a5bb81-9a86-8901-31dd-dc9c09da0a23@gmail.com>

On Mon, 19 Apr 2021 at 12:10, Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> On 19/04/21 16.11, Cristian Morales Vega wrote:
> > Basically after something updates the ctime of a file, a
> > "git checkout" can behave differently depending on whether a
> > "git update-index --refresh" has been run before or not.
> > _Maybe_ it could make sense for "git checkout" to always behave as if
> > "git update-index --refresh" had been run before? No idea really.
> I know that setting SELinux label can alter file ctime, but when
> I need to write the test that simulate file ctime update, do you
> know which Unix command can trigger that, beside SELinux tools?

I am no expert on SELinux and I'm not sure I understand the question.
I know "chcon", from coreutils, can do the SELinux labeling/ctime
update. You could use that when writing a test. There is an example on
the fifth comment of JENKINS-65395.
I know "docker run --volume <host-dir>:<container-dir>:rw,z" will do
the same, at least if SELinux is enabled. Which is what triggers
JENKINS-65395.
Don't really know a lot more.

  reply	other threads:[~2021-04-19 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19  9:11 git checkout behaviour when only ctime of file changes Cristian Morales Vega
2021-04-19 11:10 ` Bagas Sanjaya
2021-04-19 11:23   ` Cristian Morales Vega [this message]
2021-04-19 20:47 ` Junio C Hamano
2021-04-20  2:04 ` brian m. carlson
2021-04-20  6:10   ` Cristian Morales Vega

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='CAOWQn3Qa68aWH8ztGAej=ctJDw4dkzuPQkkqo6Ydvn=13hV1vw@mail.gmail.com' \
    --to=christian.morales.vega@gmail.com \
    --cc=bagasdotme@gmail.com \
    --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. 
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).