From: "René Scharfe" <l.s.r@web.de>
To: Jeff King <peff@peff.net>, PANEL Christian <ch.panel@free.fr>
Cc: git@vger.kernel.org
Subject: Re: git bug
Date: Mon, 10 Aug 2020 07:56:13 +0200 [thread overview]
Message-ID: <c223cb39-501f-8ed1-9b82-2f7c2cb22886@web.de> (raw)
In-Reply-To: <20200807000226.GA12088@coredump.intra.peff.net>
Am 07.08.20 um 02:02 schrieb Jeff King:
> On Thu, Aug 06, 2020 at 10:23:54PM +0200, René Scharfe wrote:
>
>> So "file" is no longer ignored. Committing the .gitignore change
>> doesn't change that:
>>
>> $ git add .gitignore
>> $ git commit -m 2nd
>> [master d4c95a1] 2nd
>> 1 file changed, 1 deletion(-)
>> $ git status
>> On branch master
>> Untracked files:
>> (use "git add <file>..." to include in what will be committed)
>> file
>>
>> nothing added to commit but untracked files present (use "git add" to track)
>>
>> Which steps did you take to arrive at a different result?
>
> Perhaps also:
>
> git check-ignore -v file
>
> would be helpful for seeing why Git thinks it might be ignored (e.g.,
> another wildcard rule that happens to match it).
Right. And there is more than one possible place to specify files to be
ignored. E.g. you can use info/exclude in your Git directory (i.e.
.git/info/exclude by default) for repository-specific patterns don't
want to share. See https://git-scm.com/docs/gitignore or the manpage
of gitignore(5) for more details.
René
next prev parent reply other threads:[~2020-08-10 5:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 14:48 git bug PANEL Christian
2020-08-06 20:23 ` René Scharfe
2020-08-07 0:02 ` Jeff King
2020-08-10 5:56 ` René Scharfe [this message]
2020-08-10 17:20 ` PANEL Christian
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 19:32 Justin Tang
2024-02-04 23:42 moti sd
2024-02-05 6:47 ` Patrick Steinhardt
2023-04-14 9:41 Git bug Gabriel Furstenheim Milerud
2023-04-14 16:07 ` René Scharfe
[not found] ` <CAJN3DWpvh8uHnRFnaPgg8U6dW=3xP9YULBe-xfeTAg2SV7K+oQ@mail.gmail.com>
2023-04-17 9:46 ` Gabriel Furstenheim Milerud
2023-04-14 8:29 Gabriel Furstenheim Milerud
2023-04-14 9:26 ` Kristoffer Haugsbakk
2020-08-06 14:59 git bug PANEL Christian
2012-10-22 16:28 git BUG Коньков Евгений
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=c223cb39-501f-8ed1-9b82-2f7c2cb22886@web.de \
--to=l.s.r@web.de \
--cc=ch.panel@free.fr \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).