merge-ort: loosen commented requirements
The comment above type_short_descriptions claimed that the order had to match what was found in the conflict_info_and_types enum. Since type_short_descriptions uses designated initializers, the order should not actually matter; I am guessing that positional initializers may have been under consideration when that comment was added, but the comment was not updated when designated initializers were chosen. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
5fadf1f933
commit
c55c3f20b1
@ -553,7 +553,7 @@ enum conflict_and_info_types {
|
||||
* Short description of conflict type, relied upon by external tools.
|
||||
*
|
||||
* We can add more entries, but DO NOT change any of these strings. Also,
|
||||
* Order MUST match conflict_info_and_types.
|
||||
* please ensure the order matches what is used in conflict_info_and_types.
|
||||
*/
|
||||
static const char *type_short_descriptions[] = {
|
||||
/*** "Simple" conflicts and informational messages ***/
|
||||
|
Loading…
Reference in New Issue
Block a user