From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Ok to backport Eshell manual improvements to 29? Date: Fri, 14 Jul 2023 10:22:29 +0300 Message-ID: <838rbj3qkq.fsf@gnu.org> References: <871qhcjnb7.fsf@gmx.de> <1ccb1cae-1eb1-79ce-71bd-133d9d679c5a@gmail.com> <86o7kft1db.fsf@mail.linkov.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10040"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jporterbugs@gmail.com, emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 14 09:22:42 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qKD8T-0002ND-IC for ged-emacs-devel@m.gmane-mx.org; Fri, 14 Jul 2023 09:22:41 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qKD87-0007aw-By; Fri, 14 Jul 2023 03:22:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qKD80-0007aX-GW for emacs-devel@gnu.org; Fri, 14 Jul 2023 03:22:12 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qKD7z-0001hA-K6; Fri, 14 Jul 2023 03:22:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=MeyrXhy+1FRj3imF1wyz6ELHn5hPbPQEH6zltBg88qM=; b=GEWIrEZ6ckJc LV9FZPC35s8FmaAk7cSkwlaMsRsxk0lyrz6l7V9Xagv3sgAfzDRyadXQvS7hqne3YnZlpqZPqIbq6 hXAmABBs2DMq1bZN2/+FI2SlQQ14iqfm9UmZFocEshduG4XnUPSRcD++cO4T79ECHYRpK0LWGTsQV iZlAsxdGifWbUT6f71qwqH6jLysnIBhEyWIYn4yarUmuoq/DPMzXM64ZRBZ8vA0iLfIm55JEZaIUz fgZ2MeSagQp7S7EnHBisqVQcc2NDSDkzCBXu1BT0PfKBSi8FIaPy13uqFPT+BiKej2NJ97AwEHDYO Zry80+nPdjp+w9az6n9FYg==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qKD7z-0005df-37; Fri, 14 Jul 2023 03:22:11 -0400 In-Reply-To: <86o7kft1db.fsf@mail.linkov.net> (message from Juri Linkov on Fri, 14 Jul 2023 10:10:13 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:307857 Archived-At: > From: Juri Linkov > 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.