all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: luangruo@yahoo.com, schwab@linux-m68k.org,
	gerd.moellmann@gmail.com, emacs-devel@gnu.org
Subject: Re: Absentee log entry and Git question
Date: Thu, 09 May 2024 12:52:28 +0300	[thread overview]
Message-ID: <861q6b71nn.fsf@gnu.org> (raw)
In-Reply-To: <87msoz9uzz.fsf@aarsen.me> (message from Arsen Arsenović on Thu, 09 May 2024 11:48:00 +0200)

> From: Arsen Arsenović <arsen@aarsen.me>
> Cc: Po Lu <luangruo@yahoo.com>,  schwab@linux-m68k.org,
>  gerd.moellmann@gmail.com,  emacs-devel@gnu.org
> Date: Thu, 09 May 2024 11:48:00 +0200
> 
> > The VC log is carved in stone with Git, so it cannot be corrected.
> >
> > We _can_ correct that in the generated ChangeLog file, though.  To
> > this end, one needs to generate ChangeLog.4, then edit it, and then
> > commit the fixed version.  This can be done now, or it can be deferred
> > until the first pretest tarball is made for the next version.
> 
> Could an empty commit with just the missing ChangeLog hunk work? It can
> be created using:
> 
>   git commit --allow-empty

It won't help, so no.

> BTW, it might make sense to reuse/reimplement some of the git
> infrastructure GCC uses to prevent pushes without matching ChangeLogs.

We already have such hooks, but that commit was more than 6 months
ago.



  reply	other threads:[~2024-05-09  9:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87edab30yq.fsf.ref@yahoo.com>
2024-05-09  7:21 ` Absentee log entry and Git question Po Lu
2024-05-09  7:48   ` Gerd Möllmann
2024-05-09  8:08     ` Po Lu
2024-05-09  8:11       ` Andreas Schwab
2024-05-09  8:22         ` Po Lu
2024-05-09  9:43           ` Eli Zaretskii
2024-05-09  9:48             ` Arsen Arsenović
2024-05-09  9:52               ` Eli Zaretskii [this message]
2024-05-09 10:41           ` Sean Allred
2024-05-09  8:08     ` tomas

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=861q6b71nn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=arsen@aarsen.me \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=luangruo@yahoo.com \
    --cc=schwab@linux-m68k.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 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.