[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: stale git branches
|
From: |
Han-Wen Nienhuys |
|
Subject: |
Re: stale git branches |
|
Date: |
Sat, 11 Apr 2020 14:48:05 +0200 |
On Sat, Apr 11, 2020 at 2:13 PM Jonas Hahnfeld <address@hidden> wrote:
> following removal of dev/translation-* branches, I took a closer look
> at stale branches. I think it would make sense to keep unscoped
> branches (outside of dev/user/) to a minimum. This should also avoid
> overlooking old changes that have not been merged yet.
> The following list is by no means complete, but maybe a good start:
>
> dev/pango contains commits:
> 53ed2b55e2 Add a RAII wrapper for extracting FT_Face from PangoFcFont
> c93c477180 Make Pango >= 1.36 mandatory.
> in master:
> 9cf8d35e8c Add a RAII wrapper for extracting FT_Face from PangoFcFont
> 15b7118410 Make Pango >= 1.36 mandatory.
> I'm fairly certain the branch can be removed.
This can be removed. It was a staging area when David wanted to revert
said patch from staging.
> As far as I understand, master now also has the relevant commits from
> dev/guile-v2-work, dev/guilev2, and dev/guilev21? Can those branches be
> dropped to avoid possible confusion about the current status?
I think so.
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen