From: Claus Schneider Date: Tue, 10 Mar 2026 21:10:14 GMT Subject: Re: [PATCH v4 5/5] Documentation: update add --force option + ignore=all config Message-ID: In-Reply-To: Hi Kristoffer, I am unsure about submitting these fixes now, as the patch appears to have already been merged. I could add it as a 6th patch, and merging would still work fine instead of amending the 5th patch - please let me know what is the best way to proceed Best regards, Claus Schneider On Tue, Mar 10, 2026 at 10:04 PM Claus Schneider wrote: > > Hi .. > > Thanks .. I will fix both. > > Br > Claus Schneider > > On Wed, Mar 4, 2026 at 3:02 PM Kristoffer Haugsbakk > wrote: > > > > On Fri, Feb 6, 2026, at 14:23, Claus Schneider(Eficode) via GitGitGadget wrote: > > > From: "Claus Schneider(Eficode)" > > > > > > - git-add.adoc: Update the --force documentation for submodule behaviour > > > to be added even the given configuration ignore=all. > > > - gitmodules.adoc and config/submodule.adoc: The submodule config > > > ignore=all now need --force in order to update the index. > > > > > > Signed-off-by: Claus Schneider(Eficode) > > >[snip] > > > all;; The submodule will never be considered modified (but will > > > nonetheless show up in the output of status and commit when it has > > > - been staged). > > > + been staged). Add `(new commits)` can be overruled using the > > > + `git add --force `. > > > + The setting affects `status`, `update-index`, `diff` and `log`(due > > > > This is in `next` but: should be a space: “`log` (due”. > > > > > + to underlaying `diff`). > > > > s/underlaying/underlying/ ? > > > > > > > > dirty;; All changes to the submodule's work tree will be ignored, only > > > committed differences between the `HEAD` of the submodule and its > > > -- > > > gitgitgadget