Given that, in the end, the change is rather small and involves just one file, having it be just one commit is fine. Perhaps my next lesson to learn is to generate and send the patch sets myself, but that will be for another time. Thank you for all your patience, it makes a total noob like me feel welcome. On Thu, Aug 11, 2022 at 1:53 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Eric D <eric.decosta@xxxxxxxxx> writes: > > > Well, needless to say I wasn't expecting GitGitGadget to do what it > > did.I had squashed things down to just two commits and forced-pushed > > the second commit thinking that just the relevant stuff from the > > second commit would show up in the next patch. Obviously that didn't > > happen. Sorry about that. > > Oh, sorry to hear that. If your ideal "logical progression" needs > two commits, then please do present the series that way. What GGG > sent out was apparently not that (i.e. the same one from v1 with > full of fix-ups for it in 2/2). >
