[Top][All Lists]

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

Re: git history tracking across renames (and emacs support) (Was: The na

From: Paul Eggert
Subject: Re: git history tracking across renames (and emacs support) (Was: The name gnus-cloud.el)
Date: Tue, 2 Jan 2018 00:06:11 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0

Richard Stallman wrote:
Was the whole history of our repository lost at that time ???

Not at all. It's still there.

As part of maintenance I've done quite a bit of spelunking through the history of Emacs and other GNU programs, and the problem of following renames is small potatoes compared to the issues that normally consume most of my software-archaeology time: namely, figuring out *why* a change was made, not the mechanical details of what changed.

What would be most helpful (and I realize I'm asking for a lot) would be ChangeLog entries or commit messages (it doesn't matter which) that explain the *motivation* for each change. In contrast, often it is counterproductive to burden commit messages with mechanical details such as naming each and every function that was modified, as it wastes developers' time to wade through these details when they're trying to look for stuff that's more important.

reply via email to

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