merge-recursive: distinguish "removed" and "overwritten" messages
To limit the number of possible error messages, the error messages for the case would_lose_untracked_file and would_lose_orphaned in unpack_trees_options.msgs were handled with a single string, parameterized by an action string ("overwritten" or "removed"). Instead, we consider them as two different cases, with unparameterized string. This will make it easier to make separate lists sorted by error types later. Only the bind_overlap case still takes two %s parameters, but that's unavoidable. Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
23cbf11b5c
commit
08402b0409
@ -13,10 +13,12 @@ enum unpack_trees_error_types {
|
||||
ERROR_WOULD_OVERWRITE = 0,
|
||||
ERROR_NOT_UPTODATE_FILE,
|
||||
ERROR_NOT_UPTODATE_DIR,
|
||||
ERROR_WOULD_LOSE_UNTRACKED,
|
||||
ERROR_WOULD_LOSE_UNTRACKED_OVERWRITTEN,
|
||||
ERROR_WOULD_LOSE_UNTRACKED_REMOVED,
|
||||
ERROR_BIND_OVERLAP,
|
||||
ERROR_SPARSE_NOT_UPTODATE_FILE,
|
||||
ERROR_WOULD_LOSE_ORPHANED,
|
||||
ERROR_WOULD_LOSE_ORPHANED_OVERWRITTEN,
|
||||
ERROR_WOULD_LOSE_ORPHANED_REMOVED,
|
||||
NB_UNPACK_TREES_ERROR_TYPES
|
||||
};
|
||||
|
||||
|
Reference in New Issue
Block a user