all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>, dick <dick.r.chiang@gmail.com>
Cc: 54359@debbugs.gnu.org
Subject: bug#54359: 29.0.50; [PATCH] Undo breaking change to project interface
Date: Fri, 18 Mar 2022 02:58:43 +0200	[thread overview]
Message-ID: <6da09744-feb3-b3c8-a47f-2dd086ccd509@yandex.ru> (raw)
In-Reply-To: <87h780yg1w.fsf@gnus.org>

On 14.03.2022 12:38, Lars Ingebrigtsen wrote:
> dick<dick.r.chiang@gmail.com>  writes:
> 
>> Subject: [PATCH] Avoid breaking the world's `project-current` calls
>>
>> mitigate 86969f9.
> It's unclear what the problem here is, but it'll be obvious to Dmitry,
> so I've added him to the CCs.

It might be able to guess what Dick meant, but it's only going to be a 
guess without a proper bug report description.

But to address the title: there was no breaking change to the public 
interface.

A data structure internal to the vc project backend has changed, though.





  reply	other threads:[~2022-03-18  0:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-12 21:47 bug#54359: 29.0.50; [PATCH] Undo breaking change to project interface dick
2022-03-13  5:48 ` Eli Zaretskii
2022-03-14 19:35   ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-17 11:28     ` Lars Ingebrigtsen
2022-03-18  0:56       ` Dmitry Gutov
2022-03-18  9:33         ` Lars Ingebrigtsen
2022-03-18 11:02           ` dick
2022-03-18 11:27           ` Dmitry Gutov
2022-03-18 12:09             ` dick
2022-03-19 18:57               ` Juri Linkov
2022-03-19 14:19             ` Lars Ingebrigtsen
2022-03-19 23:45               ` Dmitry Gutov
2022-03-14 10:38 ` Lars Ingebrigtsen
2022-03-18  0:58   ` Dmitry Gutov [this message]
2022-03-18  1:13     ` dick
2022-03-18 11:25       ` Dmitry Gutov

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=6da09744-feb3-b3c8-a47f-2dd086ccd509@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=54359@debbugs.gnu.org \
    --cc=dick.r.chiang@gmail.com \
    --cc=larsi@gnus.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.