unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19113@debbugs.gnu.org
Subject: bug#19113: Generate a ChangeLog file from commit logs
Date: Thu, 20 Nov 2014 09:43:59 -0800	[thread overview]
Message-ID: <546E285F.7040604@cs.ucla.edu> (raw)
In-Reply-To: <837fyp7tvi.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 415 bytes --]

On 11/20/2014 07:51 AM, Eli Zaretskii wrote:
> What's the plan for preventing the generated ChangeLog file from
> becoming too large?
I added an --until option to gitlog-to-changelog so that we can generate 
a set of ChangeLogs rather than a single ChangeLog.  We can uses this 
once we want to generate multiple ChangeLogs.  I'll CC: this email to 
bug-gnulib since the source belongs to gnulib.  Patch attached.


[-- Attachment #2: 0001-gitlog-to-changelog-add-until.patch --]
[-- Type: text/x-patch, Size: 2707 bytes --]

From 44545ded16ccb5985107c02ab0c9effedc9b0b0c Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Thu, 20 Nov 2014 09:29:35 -0800
Subject: [PATCH] gitlog-to-changelog: add --until

* build-aux/gitlog-to-changelog: Support new --until option.
Need described by Eli Zaretskii in: http://bugs.gnu.org/19113
---
 ChangeLog                     | 6 ++++++
 build-aux/gitlog-to-changelog | 7 ++++++-
 2 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index 16dc620..8473384 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2014-11-20  Paul Eggert  <eggert@cs.ucla.edu>
+
+	gitlog-to-changelog: add --until
+	* build-aux/gitlog-to-changelog: Support new --until option.
+	Need described by Eli Zaretskii in: http://bugs.gnu.org/19113
+
 2014-11-14  Paul Eggert  <eggert@cs.ucla.edu>
 
 	extern-inline: update commentary about GCC bugs
diff --git a/build-aux/gitlog-to-changelog b/build-aux/gitlog-to-changelog
index 78afff4..190f7b5 100755
--- a/build-aux/gitlog-to-changelog
+++ b/build-aux/gitlog-to-changelog
@@ -3,7 +3,7 @@ eval '(exit $?0)' && eval 'exec perl -wS "$0" ${1+"$@"}'
     if 0;
 # Convert git log output to ChangeLog format.
 
-my $VERSION = '2012-07-29 06:11'; # UTC
+my $VERSION = '2014-11-20 17:25'; # UTC
 # The definition above must lie within the first 8 lines in order
 # for the Emacs time-stamp write hook (at end) to update it.
 # If you change this file with Emacs, please let the write hook
@@ -72,6 +72,7 @@ OPTIONS:
                   directory can be derived.
    --since=DATE convert only the logs since DATE;
                   the default is to convert all log entries.
+   --until=DATE convert only the logs older than DATE.
    --format=FMT set format string for commit subject and body;
                   see 'man git-log' for the list of format metacharacters;
                   the default is '%s%n%b%n'
@@ -220,6 +221,7 @@ sub git_dir_option($)
 
 {
   my $since_date;
+  my $until_date;
   my $format_string = '%s%n%b%n';
   my $amend_file;
   my $append_dot = 0;
@@ -232,6 +234,7 @@ sub git_dir_option($)
      help => sub { usage 0 },
      version => sub { print "$ME version $VERSION\n"; exit },
      'since=s' => \$since_date,
+     'until=s' => \$until_date,
      'format=s' => \$format_string,
      'amend=s' => \$amend_file,
      'append-dot' => \$append_dot,
@@ -243,6 +246,8 @@ sub git_dir_option($)
 
   defined $since_date
     and unshift @ARGV, "--since=$since_date";
+  defined $until_date
+    and unshift @ARGV, "--until=$until_date";
 
   # This is a hash that maps an SHA1 to perl code (i.e., s/old/new/)
   # that makes a correction in the log or attribution of that commit.
-- 
1.9.3


  reply	other threads:[~2014-11-20 17:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 23:57 bug#19113: Generate a ChangeLog file from commit logs Paul Eggert
2014-11-20 15:51 ` Eli Zaretskii
2014-11-20 17:43   ` Paul Eggert [this message]
2014-11-20 17:44   ` Paul Eggert
2014-11-26  5:38     ` Paul Eggert
2014-11-26  6:21       ` Jan D.
2014-11-26  7:50         ` Paul Eggert
2014-11-26 15:12       ` Stefan Monnier
2014-11-26 19:16         ` Paul Eggert
2014-11-26 22:15           ` Stefan Monnier
2014-12-05  8:07           ` Glenn Morris
2014-12-05  8:38             ` Eli Zaretskii
2014-12-05 14:33             ` Ted Zlatanov
2014-12-05 18:49               ` Stefan Monnier
2014-12-05 20:08                 ` Ted Zlatanov
2014-12-06  4:59                   ` Stefan Monnier
2014-12-06 13:17                     ` Ted Zlatanov
2014-12-06  2:27                 ` Dmitry Gutov
2014-12-06  5:06                   ` Stefan Monnier
2014-12-06  7:26                     ` Eli Zaretskii
2014-12-09 13:46                     ` Dmitry Gutov
2014-12-05 15:38             ` Stefan Monnier
2014-12-06  4:42               ` Paul Eggert
2014-12-06  7:40                 ` Eli Zaretskii
2014-12-09  5:14                 ` Glenn Morris
2014-12-09  6:42                   ` Paul Eggert
2015-01-03  1:37             ` Glenn Morris
2014-11-20 18:00   ` Achim Gratz
2014-11-20 17:25 ` Pádraig Brady
2015-01-12  7:38 ` Paul Eggert
2015-01-15 14:58   ` Stefan Monnier
2015-01-15 21:46   ` Glenn Morris
2015-01-16  1:27     ` Paul Eggert
2015-01-30 16:34       ` Stefan Monnier
2015-01-30 20:14         ` Paul Eggert
2015-01-31  6:33           ` Stefan Monnier
2015-01-31  8:18             ` Paul Eggert
2015-01-31  9:06           ` Andreas Schwab
2015-03-21  2:37 ` Paul Eggert
2015-03-21  8:33   ` Eli Zaretskii
2015-03-21 14:38     ` Stefan Monnier
2015-03-22 23:53   ` Glenn Morris
2015-04-07  7:06   ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=546E285F.7040604@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=19113@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).