[Top][All Lists]

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

bug#19113: Generate a ChangeLog file from commit logs

From: Eli Zaretskii
Subject: bug#19113: Generate a ChangeLog file from commit logs
Date: Fri, 05 Dec 2014 10:38:08 +0200

> From: Glenn Morris <address@hidden>
> Date: Fri, 05 Dec 2014 03:07:07 -0500
> Cc: address@hidden
> 4) What if I commit something, realize it was wrong, and remove it right
> away? Normally I'd delete the ChangeLog entry too.

With Git, it's useful to distinguish between "commit" and "push".  The
former can be easily fixed, since it's still only in your local clone;
use "git amend" or even "git reset".  The latter cannot be fixed,
except by running Git commands on Savannah that work directly on the
public repository, which is generally frowned upon, because others
could have pulled in-between.

> 6) How does the correction method work (I'm being lazy and not reading
> the patch).

>From "gitlog-to-changelog --help:

    --amend=FILE FILE maps from an SHA1 to perl code (i.e., s/old/new/) that
                   makes a change to SHA1's commit log text or metadata.
  In a FILE specified via --amend, comment lines (starting with "#") are 
  FILE must consist of <SHA,CODE+> pairs where SHA is a 40-byte SHA1 (alone on
  a line) referring to a commit in the current project, and CODE refers to one
  or more consecutive lines of Perl code.  Pairs must be separated by one or
  more blank line.

  Here is sample input for use with --amend=FILE, from coreutils:

  # fix typo in title:
  s/all tile types/all file types/

  # Due to a bug in vc-dwim, I mis-attributed a patch by Paul to myself.
  # Change the author to be Paul.  Note the escaped "@":
  s,Jim .*>,Paul Eggert <address@hidden>,

reply via email to

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