Skip to content

mv from in-cone to out-of-cone #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ffyuanda wants to merge 4 commits into
base: mv-v5
Choose a base branch
from
Open

mv from in-cone to out-of-cone #3

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8063b21
t7002: add tests for moving from in-cone to out-of-cone
ffyuanda Jun 30, 2022
29400d6
mv: check if <destination> is a directory in the index with
ffyuanda Jun 21, 2022
044cd40
mv: rename BOTH flag to DEFAULT
ffyuanda Jun 21, 2022
34b53e9
mv: from in-cone to out-of-cone
ffyuanda Jun 22, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion builtin/mv.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ static const char * const builtin_mv_usage[] = {
};

enum update_mode {
BOTH = 0,
DEFAULT = 0,
Copy link
Copy Markdown

@vdye vdye Jul 11, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than rename this, why not remove it entirely? The elements of this enum are being treated as flags, but 0 isn't really a "flag" value - you don't |= it to "apply" it (it's not even really "applied"), and it's mutually exclusive with all the other flag values.

Since it's (as far as I can tell?) not used explicitly anywhere, I think it's more confusing than not to keep it.

WORKING_DIRECTORY = (1 << 1),
INDEX = (1 << 2),
SPARSE = (1 << 3),
Expand Down