From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: jporterbugs@gmail.com, emacs-devel@gnu.org
Subject: Re: Ok to backport Eshell manual improvements to 29?
Date: Fri, 14 Jul 2023 10:22:29 +0300 [thread overview]
Message-ID: <838rbj3qkq.fsf@gnu.org> (raw)
In-Reply-To: <86o7kft1db.fsf@mail.linkov.net> (message from Juri Linkov on Fri, 14 Jul 2023 10:10:13 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: emacs-devel@gnu.org
> Date: Fri, 14 Jul 2023 10:10:13 +0300
>
> > Now merged to the emacs-29 branch as 6a360b08405.
>
> Is there a policy that requires deleting a merged branch?
They should be deleted eventually, but we don't require them to be
deleted as soon as they land on the main branches. It is up to the
branch owner to decide when to delete the branch; there could be
reasons to wait for some short time, like if any leftovers are
anticipated that are easier handled on the branch.
next prev parent reply other threads:[~2023-07-14 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 1:52 Ok to backport Eshell manual improvements to 29? Jim Porter
2023-07-13 7:14 ` Michael Albinus
2023-07-13 16:10 ` Jim Porter
2023-07-14 2:26 ` Jim Porter
2023-07-14 7:10 ` Juri Linkov
2023-07-14 7:22 ` Eli Zaretskii [this message]
2023-07-14 16:29 ` Jim Porter
2023-07-14 16:52 ` Juri Linkov
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=838rbj3qkq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=juri@linkov.net \
/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.