From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: Pruning dead branches
Date: Mon, 24 Jan 2022 01:13:50 +0200 [thread overview]
Message-ID: <c0d99bfa-8e22-832a-9882-95aa60950fe2@yandex.ru> (raw)
In-Reply-To: <875yqa6zz7.fsf@gnus.org>
On 23.01.2022 20:58, Lars Ingebrigtsen wrote:
> I've got through the list and deleted "my" branches that I'd forgotten
> to delete, but could everybody else also do that and see if they've
> forgotten branches?
Did so now, thanks for the reminder.
next prev parent reply other threads:[~2022-01-23 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 18:58 Pruning dead branches Lars Ingebrigtsen
2022-01-23 20:58 ` Stefan Kangas
2022-01-24 9:34 ` Lars Ingebrigtsen
2022-01-23 23:13 ` Dmitry Gutov [this message]
2022-01-24 6:04 ` Phil Sainty
2022-01-30 16:56 ` Juri Linkov
2022-01-30 17:43 ` Lars Ingebrigtsen
2022-01-30 18:30 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0d99bfa-8e22-832a-9882-95aa60950fe2@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).