From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: git@vger.kernel.org
Subject: No error when overwriting ignored files
Date: Wed, 7 Apr 2021 15:56:38 -0400 (CLT) [thread overview]
Message-ID: <2056254759.360640.1617825398727.JavaMail.zimbra@inf.utfsm.cl> (raw)
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
When pulling from a repository that tracks a file listed in `.gitignore` that would overwrite a local file, this is not reported.
For example, in the attached repositories, when doing `git pull tst1` in `tst2`, it is (correctly) reported that `ignored.not` would be overwritten, while `ignored.txt` is not reported.
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria +56 32 2654239
Casilla 110-V, Valparaiso, Chile 2340000 Fax: +56 32 2797513
[-- Attachment #2: tstrepos.tgz --]
[-- Type: application/x-gzip, Size: 21878 bytes --]
next reply other threads:[~2021-04-07 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 19:56 Horst von Brand [this message]
2021-04-07 20:18 ` No error when overwriting ignored files Jeff King
2021-04-07 22:17 ` Ævar Arnfjörð Bjarmason
2021-04-07 20:47 ` Junio C Hamano
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=2056254759.360640.1617825398727.JavaMail.zimbra@inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--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).