From: Paul Smith <psmith@gnu.org>
To: Mike Frysinger <vapier@gentoo.org>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: sim: replacing ChangeLog files with online git logs
Date: Sat, 13 Mar 2021 13:34:40 -0500 [thread overview]
Message-ID: <5fef4259b3b645179173fb9891f4a7221213ed13.camel@gnu.org> (raw)
In-Reply-To: <YE0CqWkmgP897HmE@vapier>
On Sat, 2021-03-13 at 13:21 -0500, Mike Frysinger via Gdb wrote:
> > > the hard & bikeshed part is what form does the log take. do you
> > > just want the default `git log` output ?
> > There's a Gnulib script which will produce the form that matches
> > the ChangeLog format.
>
> there's actually multiple gnulib scripts. which one are you
> referring to ? gitlog-to-changelog ?
I have no interest in getting in the middle of the discussion on what
is appropriate or not, but FYI this is the text I add to the maintainer
version of the makefile for GNU make, if it helps (the gl2cl-date
variable holds the oldest date to be included in the ChangeLog).
## ---------------------- ##
## Generating ChangeLog. ##
## ---------------------- ##
gl2cl-date := 2013-10-10
gl2cl := $(GNULIBDIR)/build-aux/gitlog-to-changelog
# Rebuild the changelog whenever a new commit is added
ChangeLog: .check-git-HEAD
if test -f '$(gl2cl)'; then \
'$(gl2cl)' --since='$(gl2cl-date)' > '$@'; \
else \
echo "WARNING: $(gl2cl) is not available. No $@ generated."; \
fi
.check-git-HEAD: FORCE
sha="`git rev-parse HEAD`"; \
test -f '$@' && [ "`cat '$@' 2>/dev/null`" = "$$sha" ] \
|| echo "$$sha" > '$@'
.PHONY: FORCE
FORCE:;@:
prev parent reply other threads:[~2021-03-13 18:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 2:53 Mike Frysinger
2021-03-13 7:30 ` Eli Zaretskii
2021-03-13 15:12 ` Mike Frysinger
2021-03-13 16:02 ` Eli Zaretskii
2021-03-13 16:26 ` Mike Frysinger
2021-03-13 16:38 ` Eli Zaretskii
2021-03-13 18:21 ` Mike Frysinger
2021-03-13 18:32 ` Eli Zaretskii
2021-03-17 6:07 ` Mike Frysinger
2021-03-17 13:14 ` Eli Zaretskii
2021-03-17 14:31 ` Luis Machado
2021-03-17 14:47 ` Eli Zaretskii
2021-03-17 14:52 ` Luis Machado
2021-03-17 15:09 ` Eli Zaretskii
2021-03-17 15:22 ` Luis Machado
2021-03-17 15:40 ` Eli Zaretskii
2021-03-17 15:52 ` Simon Marchi
2021-03-17 16:09 ` Eli Zaretskii
2021-03-17 17:24 ` Luis Machado
2021-03-17 17:53 ` Eli Zaretskii
2021-03-17 20:53 ` Luis Machado
2021-03-18 9:31 ` Andrew Burgess
2021-03-18 9:48 ` Eli Zaretskii
2021-03-22 2:19 ` Maciej W. Rozycki
2021-03-22 3:38 ` Eli Zaretskii
2021-03-23 4:57 ` Mike Frysinger
2021-03-23 5:05 ` Mike Frysinger
2021-03-23 11:06 ` Andrew Burgess
2021-03-24 3:45 ` Mike Frysinger
2021-03-24 16:46 ` Eli Zaretskii
2021-03-24 16:59 ` Andrew Burgess
2021-03-24 17:39 ` Eli Zaretskii
2021-03-24 18:44 ` Mike Frysinger
2021-03-31 2:27 ` Mike Frysinger
2021-03-31 3:27 ` Joel Brobecker
2021-03-31 11:35 ` Luis Machado
2021-03-31 15:29 ` Joel Brobecker
2021-04-01 3:41 ` Mike Frysinger
2021-04-19 0:52 ` Mike Frysinger
2021-04-19 2:32 ` Joel Brobecker
2021-04-19 4:31 ` Mike Frysinger
2021-04-19 5:00 ` Joel Brobecker
2021-05-23 3:26 ` Mike Frysinger
2021-06-10 12:11 ` Luis Machado
2021-03-13 18:34 ` Paul Smith [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5fef4259b3b645179173fb9891f4a7221213ed13.camel@gnu.org \
--to=psmith@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=vapier@gentoo.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.
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).