|
From: | Dmitry Gutov |
Subject: | bug#38044: 27.0.50; There should be an easier way to look at a specific vc commit |
Date: | Thu, 21 Nov 2019 17:34:00 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 |
On 21.11.2019 16:59, Eli Zaretskii wrote:
The reason I think this should be a vc-diff subcommand is that most kinds of VCS describe a revision as diffs.
I strongly disagree with that idea.When we create a revision, we specify both the changes, *and* a commit message. And some other metadata, like author, etc.
That happens in *every* VCS I had worked with, starting with CVS.So no, a revision can't be described simply by a diff. The info should include all of the above.
Any VCS that doesn't support commit messages, etc, can simply show a diff. But we shouldn't cater to the lowest commit denominator in the API.
[Prev in Thread] | Current Thread | [Next in Thread] |