all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sean Allred <allred.sean@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: "Andreas Schwab" <schwab@linux-m68k.org>,
	"Gerd Möllmann" <gerd.moellmann@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Absentee log entry and Git question
Date: Thu, 09 May 2024 05:41:36 -0500	[thread overview]
Message-ID: <m0jzk3xo06.fsf@epic96565.epic.com> (raw)
In-Reply-To: <87ttj71jjr.fsf@yahoo.com>


Po Lu <luangruo@yahoo.com> writes:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>> No.
> Alright, so how should this error be corrected in the VC log and
> generated ChangeLog files?

I tend to think this would be an over-engineered solution unless this
happens often, but if you're sufficiently-motivated, you could look at
using notes refs for this purpose.[1] git-notes are intended (for the
most part) to add information to existing history, so a system could
certainly be constructed during changelog gen that would read from a
note as well if it exists (or perhaps in an overriding fashion).

If you do go down this route, please CC me; I'd be interested to see
where you end up.

[1]: https://git-scm.com/docs/git-notes

--
Sean Allred



  parent reply	other threads:[~2024-05-09 10:41 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
2024-05-09 10:41           ` Sean Allred [this message]
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=m0jzk3xo06.fsf@epic96565.epic.com \
    --to=allred.sean@gmail.com \
    --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.