On 7/12/23 22:33, Junio C Hamano wrote:
Side note: but is there a useful use case to set it to 'none' in
".gitmodules" in the first place? If there is not, saying that
"'none' is only useful in the configuration files" is not quite
wrong per-se.
A twisted person might use it to commit a truly empty folder, without
even a .gitkeep file. Whether that's a useful use case, I don't know.
Sounds good. s/available/allowed/, perhaps.
none;; the submodule is not updated.
++
+The `none` update procedure is only available via the .gitmodules file
+or the `submodule.<name>.update` configuration variable.
This side we do not need "only" anywhere in the sentence, do we?
Thanks.
I will address both of those and include your bugfix blurb in v3. Still
figuring out how to properly reference the previous patches using
git-send-email..
