[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: who needs script `update-patch-version`?

From: Jonas Hahnfeld
Subject: Re: who needs script `update-patch-version`?
Date: Mon, 01 Feb 2021 12:39:14 +0100
User-agent: Evolution 3.38.3

Am Montag, dem 01.02.2021 um 12:11 +0100 schrieb Werner LEMBERG:
> > 
> > > Right now I'm completely revising `programming-work.itexi`, so I
> > > can take care of that, too.
> > 
> > It would be great if you can structure the revision as incremental
> > updates and not as a big dump. Those are quite tedious to review
> > and usually take much longer to go through...
> Unfortunately, this is next to impossible since there are so many
> changes.

No, it is possible if you are willing to structure your changes in an
incremental way. For example, removing an outdated section with no
replacement should be a separate commit - easy to skip when reviewing.
Updating a particular (group of) information should be a separate
commit so that you don't have to remember all changes when reviewing.
Moving a section around should be a separate commit. And so on.

> I will provide a PDF that holds the changed pages so that you and
> others can simply read what's written there, comparing it with the
> current version of the Contributor guide if necessary.

No, large commits will make the comparison impossible because a human
is only able to remember that many details at a time. It's not about
having a PDF, it's about using git commits in a way taking advantage of
diff- and commit-based tools.

> I can also split up the commits into subchapter by subchapter, if
> that helps.

I don't see how that helps in reviewing, unless changes are local to
given sections and the next section has an unrelated set of changes
going on.


Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]