Merge branch 'jl/nor-or-nand-and'
Eradicate mistaken use of "nor" (that is, essentially "nor" used not in "neither A nor B" ;-)) from in-code comments, command output strings, and documentations. * jl/nor-or-nand-and: code and test: fix misuses of "nor" comments: fix misuses of "nor" contrib: fix misuses of "nor" Documentation: fix misuses of "nor"
This commit is contained in:
@ -790,7 +790,7 @@ void close_pack_index(struct packed_git *p)
|
||||
* contain the same set of objects as an existing one. In that case
|
||||
* the resulting file might be different even if its name would be the
|
||||
* same. It is best to close any reference to the old pack before it is
|
||||
* replaced on disk. Of course no index pointers nor windows for given pack
|
||||
* replaced on disk. Of course no index pointers or windows for given pack
|
||||
* must subsist at this point. If ever objects from this pack are requested
|
||||
* again, the new version of the pack will be reinitialized through
|
||||
* reprepare_packed_git().
|
||||
@ -1126,7 +1126,7 @@ static void report_helper(const struct string_list *list,
|
||||
const char *msg;
|
||||
switch (seen_bits) {
|
||||
case 0:
|
||||
msg = "no corresponding .idx nor .pack";
|
||||
msg = "no corresponding .idx or .pack";
|
||||
break;
|
||||
case 1:
|
||||
msg = "no corresponding .idx";
|
||||
|
Reference in New Issue
Block a user