Re: [PATCH v2 1/3] Documentation/MyFirstContribution: recommend shallow threading

I'm afraid there will be some chaos.

As mentioned earlier, GitGitGadget now supports deep nesting of iterations, if b4 changes while GitGitGadget doesn't, it would be inconsistent in the archive. So, negotiation is necessary here.

As I know, b4 can generate a cover letter containing "Changes with vn", e.g. in [PATCH v5 00/10], there would be Changes with v4, v3, v2, v1. In this case, it is semantically correct that the cover letter of v5 is replying-to the cover letter of v1.

But in traditional way, it seems that the norm is put a range-diff in the cover letter. In this case, chain-reply-to makes more sence to me: e.g. The cover letter contains the range-diff against v2, so cover letter v3 is pointing to cover letter v2. (I don't know whether git format-patch accepts several --range-diff or not, but if so, I guess it might be painful to typing several refs, or copy and paste from previous cover letter) Therefore, if git format-patch could generate cover letter containing all the changes with v4/v3/v2/v1 as b4 does, it would be consistent, and semantically correct to pointing to the first cover letter.

Do we need to consider backward compatibility here? ;-)

Thanks!