[Top][All Lists]

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

Re: Referring to revisions in the git future.

From: David Kastrup
Subject: Re: Referring to revisions in the git future.
Date: Thu, 30 Oct 2014 14:40:45 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

Stefan Monnier <address@hidden> writes:

>> to speed regarding the fine details of the discussion.  Exasperation at
>> not having used the features of Git yet seems a bit premature at a time
>> we have not even switched to Git.
> FWIW, this has nothing to do with Git, since the exact same thing could
> be done with Bzr.

Needing different tools and workflows, and Bzr was pretty much slated
for replacement when the discussion came up last time.  Regarding
readily available scripts, there was mentioning of a Git-based tool.

Deferring the ChangeLog maintenance to the version control system
requires version control to keep separate track of author and committer.
CVS doesn't.  Bzr does, Git does.  Being reasonably sure that any system
we might be using in the near future will do so as well is advisable for
switching, though of course once a ChangeLog can be generated in an
automated way, one could do so once before switching to a system
requiring manual ChangeLog maintenance.

At any rate: I certainly hope that C-x 4 a will get a _builtin_
equivalent in VC for working on commit messages.

When committing to GUILE (which wants ChangeLog style entries in its
commit messages), I currently do C-x 4 a at each source change, copy and
paste the relevant part from the resulting modified ChangeLog buffer
into the commit message, unindent it, undo the changes in the ChangeLog
buffer and kill it again, and then commit.

There must be something better than that.

David Kastrup

reply via email to

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