lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: stale git branches


From: David Kastrup
Subject: Re: stale git branches
Date: Tue, 14 Apr 2020 14:07:43 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Jonas Hahnfeld <address@hidden> writes:

> Am Samstag, den 11.04.2020, 15:33 +0200 schrieb David Kastrup:
>> Jonas Hahnfeld <address@hidden> writes:
>> 
>> > Hi all,
>> > 
>> > 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.
>> 
>> git rebase origin origin/dev/pango
>> 
>> ends up with no commit on top.  So yes.
>> 
>> > Branches dev/issue3300,
>> 
>> Mine, but actually issue 3330.  Removed.
>> 
>> > dev/issue3330, dev/issue3648 are likely related
>> > to the named issues which have status 'Verified'. AFAICS there are some
>> > additional commits in the branches, could be due to review comments?
>> > David, you are probably the best to judge if they are fully merged or
>> > some changes could still be relevant, could you take a look?
>> > 
>> > 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?
>> 
>> Will followup on all those later.
>
> I just noticed there's another branch 'vector' at the very end of the
> list. It has a single commit 'Wip' from 2012...

Probably for the sake of some discussion (I think there may have been a
SourceForge issue or a discussion on devel about it).  I have something
much better integrated with the current code base in a local branch
right now, so I'll delete.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]