Am Montag, den 24.08.2020, 09:06 +0200 schrieb Werner LEMBERG: > > I've reordered and rebased my code, and it is now up to date with > > the current master. I've just published the new branch to GitLab > as > > dev/lamb/GSoC-2020-final if you'd like to give it a look. It's > only > > nine commits now, instead of over a hundred, and they're ordered in > > a way that's hopefully easy to follow. > > Thanks! > > > At the same time, I'll write docs for my work. I figure I'll make > > nine documentation commits, one for each code change commit. (Of > > course, I may not need one for every commit, but we'll see.) Does > > that sound all right? Would it be better to make yet another > branch > > with the documentation integrated into the main commits? > > I don't see any reason to synchronize the documentation with commits; > it looks like unnecessary work. Maybe others disagree, but I think > you should simply add all of the documentation in a single, separate > commit. >
+1 But probably regtests should match the state of their commits. Except if you can add all regtests at the end. Urs > > Werner >