all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>,
	johanclaesson@bredband.net, Lars Ingebrigtsen <larsi@gnus.org>,
	emacs-devel@gnu.org
Subject: Re: master b82adee: Invalidate dir-locals-directory-cache when writing dir-local file
Date: Mon, 19 Aug 2019 11:52:15 +0200	[thread overview]
Message-ID: <87y2zp1nzk.fsf@gmail.com> (raw)
In-Reply-To: <jwv36hxy00z.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 19 Aug 2019 05:32:20 -0400")

On Mon, 19 Aug 2019 05:32:20 -0400
Stefan Monnier wrote:

>>> Oops; forgot the "Copyright-paperwork-exempt: yes", and I guess it's too
>>> late to amend after I've pushed?
>> Too late.
>
> Yup.  Hard to believe we're still stuck with this problem of "unfixable
> commit messages" after all these years.

There's "git notes", but I guess you're aware of that.

<https://git-scm.com/docs/git-notes>: "A typical use of notes is to
supplement a commit message without changing the commit itself."

-- 
Štěpán



  reply	other threads:[~2019-08-19  9:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190818224934.1914.38804@vcs0.savannah.gnu.org>
     [not found] ` <20190818224935.1ACDA20A0E@vcs0.savannah.gnu.org>
2019-08-18 22:51   ` master b82adee: Invalidate dir-locals-directory-cache when writing dir-local file Lars Ingebrigtsen
2019-08-19  2:37     ` Eli Zaretskii
2019-08-19  9:32       ` Stefan Monnier
2019-08-19  9:52         ` Štěpán Němec [this message]
2019-08-19 17:05           ` Noam Postavsky
2019-08-20  7:48             ` Štěpán Němec
2019-08-19 14:46         ` Eli Zaretskii
2019-08-19 16:45           ` Ergus via Emacs development discussions.
2019-08-19 17:25             ` Eli Zaretskii

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=87y2zp1nzk.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=johanclaesson@bredband.net \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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.