Consistently use "superproject" instead of "supermodule"
We fairly consistently say "superproject" and never "supermodule" these days. But there are seven occurrences of "supermodule" left in the current work tree. Three appear in Release Notes for 1.5.3 and 1.7.7, three in test names and one in a C-code comment. Replace all occurrences of "supermodule" outside of the Release Notes (which shouldn't be changed after the fact) with "superproject" for consistency. Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
27ccd8d1a3
commit
cb8ad289c6
@ -1209,7 +1209,7 @@ static int verify_uptodate_1(struct cache_entry *ce,
|
||||
return 0;
|
||||
/*
|
||||
* NEEDSWORK: the current default policy is to allow
|
||||
* submodule to be out of sync wrt the supermodule
|
||||
* submodule to be out of sync wrt the superproject
|
||||
* index. This needs to be tightened later for
|
||||
* submodules that are marked to be automatically
|
||||
* checked out.
|
||||
|
Reference in New Issue
Block a user