From: Achim Gratz <Stromeko@nexgo.de>
To: 19113@debbugs.gnu.org
Subject: bug#19113: Generate a ChangeLog file from commit logs
Date: Thu, 20 Nov 2014 19:00:43 +0100 [thread overview]
Message-ID: <87tx1tda5w.fsf@Gertrud.fritz.box> (raw)
In-Reply-To: <546D2E75.6090701@cs.ucla.edu>
Eli Zaretskii writes:
> What's the plan for preventing the generated ChangeLog file from
> becoming too large? Currently, we roll them over to keep the file
> below 1MB.
I haven't yet looked at what Emacs has implemented now… but you may want
to take a look at Org. The ChangeLog there is generated for only the
segment of commits between releases to Emacs. If we come up with a
reliable method to (auto-)mark the latest commit that has been picked up
for the ChangeLog, then it becomes trivial to a) do the rollover, either
manually or automatically; and b) edit entries in the ChangeLog for
style or substance that have fallen behind that barrier since the
auto-generation from commit messages will not touch them.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2014-11-20 18:00 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
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 [this message]
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=87tx1tda5w.fsf@Gertrud.fritz.box \
--to=stromeko@nexgo.de \
--cc=19113@debbugs.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).