all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Petton <nicolas@petton.fr>
Cc: 26053@debbugs.gnu.org, jwiegley@gmail.com
Subject: bug#26053: No release notice in 25.2 rc2 ChangeLog
Date: Sat, 15 Apr 2017 10:11:17 +0300	[thread overview]
Message-ID: <83efwugn6y.fsf@gnu.org> (raw)
In-Reply-To: <87mvbig09y.fsf@petton.fr> (message from Nicolas Petton on Fri, 14 Apr 2017 23:14:01 +0200)

> From: Nicolas Petton <nicolas@petton.fr>
> Cc: 26053@debbugs.gnu.org
> Date: Fri, 14 Apr 2017 23:14:01 +0200
> 
> I'm preparing the release, and I noticed that the ChangeLog file only
> contains one entry with the following:
> 
>   2017-04-14  Nicolas Petton  <nicolas@petton.fr>
>   
>   	* Version 25.2 released.
> 
> Then it directly refers to ChangeLog.2:
> 
>   See ChangeLog.2 for earlier changes.
> 
> Which is rather odd, so I looked at the 25.1 release, and it has the
> same almost empty ChangeLog file.

In 25.1, the file ChangeLog is almost empty, but the entry about 25.1
release is in ChangeLog.2.

> My question is, was it intended to have the ChangeLog file with only one
> entry (for the release)?

Not sure, but how does that ChangeLog file get created?  Which command
or Makefile rules cause its creation?





  parent reply	other threads:[~2017-04-15  7:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 22:21 bug#26053: No release notice in 25.2 rc2 ChangeLog Glenn Morris
2017-03-10 22:27 ` Glenn Morris
2017-04-14 21:14 ` Nicolas Petton
2017-04-15  1:27   ` Glenn Morris
2017-04-15  7:11   ` Eli Zaretskii [this message]
2017-04-17 17:06     ` Glenn Morris
2017-04-17 17:17       ` Eli Zaretskii
2017-04-17 17:22         ` Glenn Morris
2017-04-17 17:57           ` Eli Zaretskii
2017-04-18  9:32             ` Nicolas Petton
2017-04-18  9:30         ` Nicolas Petton
2017-04-17 17:15     ` Glenn Morris

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=83efwugn6y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26053@debbugs.gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=nicolas@petton.fr \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.