From: Jeff King <peff@peff.net>
To: Naja Melan <najamelan@autistici.org>
Cc: git@vger.kernel.org, id@joeyh.name
Subject: Re: bug when combined with etckeeper
Date: Wed, 10 Oct 2018 10:33:33 -0400 [thread overview]
Message-ID: <20181010143333.GA3854@sigill.intra.peff.net> (raw)
In-Reply-To: <4d7cddf8-34b3-eaa4-dc9e-e190062e6135@autistici.org>
On Wed, Oct 10, 2018 at 09:33:00AM +0000, Naja Melan wrote:
> I ran into a strange bug. In the following script the commit at the end will fail with:
>
> > The following paths are ignored by one of your .gitignore files:
> > .etckeeper
> > Use -f if you really want to add them.
>
> Note that there is no .gitignore file and no `.etckeeper` file in the
> repository, there is nothing in .git/exclude.
That's weird. Do you have any git-related environment variables set? Or
anything in your config that might be pointing git to an alternate
repository or working tree?
Try:
env | grep GIT
and:
git config --list --show-origin
-Peff
next prev parent reply other threads:[~2018-10-10 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 9:33 bug when combined with etckeeper Naja Melan
2018-10-10 14:33 ` Jeff King [this message]
2018-10-10 14:34 ` Joey Hess
2018-10-13 12:36 ` Naja Melan
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=20181010143333.GA3854@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=id@joeyh.name \
--cc=najamelan@autistici.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).