Samuel Lijin writes:
> After some more digging (and familiarizing myself with the
> behind-the-scenes logic) the issue is that dir.c has this implicit
> assumption that a directory which contains only untracked and ignored
> files should itself be considered untracked. While
After some more digging (and familiarizing myself with the
behind-the-scenes logic) the issue is that dir.c has this implicit
assumption that a directory which contains only untracked and ignored
files should itself be considered untracked. While that works fine for
use cases where we're asking if
On Sun, Apr 30, 2017 at 8:56 PM, Chris Johnson wrote:
> Good assessment/understanding of the issue. git clean -n does not
> report anything as being targeted for removal, and git clean -f
> matches that behavior. I agree with it probably being related
> specifically to
Chris Johnson writes:
> Also, and sorry for the noise, but I did a reply-all here, but will a
> reply automatically include the rest of the list? Or was reply-all the
> right move?
The convention around here is to do reply-all (in other words, make
sure that Cc: line
Good assessment/understanding of the issue. git clean -n does not
report anything as being targeted for removal, and git clean -f
matches that behavior. I agree with it probably being related
specifically to the -d flag.
As another experiment I modified .gitignore to ignore /A/B/C instead
of
Chris Johnson writes:
> I am a mailing list noob so I’m sorry if this is the wrong format or
> the wrong please.
>
> Here’s the setup for the bug (I will call it a bug but I half expect
> somebody to tell me I’m an idiot):
>
> git init
> echo "/A/B/" > .gitignore
You
I am a mailing list noob so I’m sorry if this is the wrong format or
the wrong please.
Here’s the setup for the bug (I will call it a bug but I half expect
somebody to tell me I’m an idiot):
git init
echo "/A/B/" > .gitignore
git add .gitignore && git commit -m 'Add ignore'
mkdir -p A/B
touch
7 matches
Mail list logo