Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106644 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 59000 invoked from network); 19 Aug 2019 04:39:20 -0000 Received: from unknown (HELO mail-qk1-f180.google.com) (209.85.222.180) by pb1.pair.com with SMTP; 19 Aug 2019 04:39:20 -0000 Received: by mail-qk1-f180.google.com with SMTP id m10so248578qkk.1 for ; Sun, 18 Aug 2019 19:09:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0S5Lj6HXZfvbOgCrTlWJE6IHh1tQbAvEOgMj1xeWi3o=; b=hmnbbGcC+jbBqQd/q3GnHEIyaZHH5NN6n+wwwQSBMA7uU7cV9gyJRLztc/OqQVe8b2 i/ZdbhPiCHTIqQO86Qrr8Tefc4cnUhvnFXGrw+j+fUubZbn25LhO6DFfuE+zyKK/ehOj ucsjyfTSYRDwpICpHk794PBB6MMb4pYaiJ6ttWp+NREDrWCpE+P53hZKjXUNA3O37jkc IUd0DJZNZDVAtGzshW6lAg5qU+xBBthVn3C3KtDomrZilIrMHCE7Qj/PNbt6febc9F9l kAUvMYHxtBGYvynCXHRSuykJ38wajDlr0EdiNRuMyZON36u1IJpoDeRrfUunwTVRDVGP KVMw== X-Gm-Message-State: APjAAAUHJX0JswmwFO9IzgrLw2sYHfNztMi6SY8iyOTQzABymSGYVqbs oFgmxjcRceniYiaco55xgIeT7a5DP+HQFEmgcgSgQw== X-Google-Smtp-Source: APXvYqxCRxpWgpGfCX4sxN1zb8VDE9XYYGBoAwnpwtSzhVVXcbPe7EsaNGcbH2ZSEaTEcwoOz9I8+HMxtVNq3P9V/C0= X-Received: by 2002:a05:620a:16d6:: with SMTP id a22mr19070506qkn.414.1566180547124; Sun, 18 Aug 2019 19:09:07 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 18 Aug 2019 21:08:56 -0500 Message-ID: To: "G. P. B." Cc: PHP internals Content-Type: multipart/alternative; boundary="0000000000002a761d05906ed366" Subject: Re: [PHP-DEV] Removing old branches in php-src From: pollita@php.net (Sara Golemon) --0000000000002a761d05906ed366 Content-Type: text/plain; charset="UTF-8" On Sun, Aug 18, 2019 at 6:06 PM G. P. B. wrote: > It seems this topic already has been raised a year ago [1] but nothing has > been done. > So I would like to raise the issue again, there are a various of old and > empty branches currently in git, would it be possible to remove them? > > 1/ Which ones *specifically*? Some release branches are empty only because they didn't need to be patched after release (and our release process was different). Some are old and even "abandoned", like the first-unicode-implementation, but they serve a useful historical purpose. 2/ Why? Git branches are lightweight and don't really impact the project in any way beyond enumerations. I'm not against getting rid of truly pointless branches, but I'm also not sure what the appeal is. -Sara --0000000000002a761d05906ed366--