Name |
Last commit
|
Last update |
---|---|---|
.. | ||
ignore.c | ||
renames.c | ||
single.c | ||
status_data.h | ||
status_helpers.c | ||
status_helpers.h | ||
submodules.c | ||
worktree.c | ||
worktree_init.c |
Given top !top/foo in an ignore file, we should not unignore top/foo. This is an implementation detail of the git code leaking, but that's the behaviour we should show. A negation rule can only negate an exact rule it has seen before.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
ignore.c | Loading commit data... | |
renames.c | Loading commit data... | |
single.c | Loading commit data... | |
status_data.h | Loading commit data... | |
status_helpers.c | Loading commit data... | |
status_helpers.h | Loading commit data... | |
submodules.c | Loading commit data... | |
worktree.c | Loading commit data... | |
worktree_init.c | Loading commit data... |