Bug#1108214: marked as done (old git branches in the repository)
Your message dated Mon, 23 Jun 2025 21:08:33 +0200
with message-id <aFmmMcKAeMkr2XD1@per.namespace.at>
and subject line Re: Bug#1108214: old git branches in the repository
has caused the Debian Bug report #1108214,
regarding old git branches in the repository
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1108214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108214
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
package: release-notes
severity: minor
The release-notes repository has accumulated some old branches that
could be deleted:
These are merged into the main history, but the branch was not deleted:
supported-archs-no-i386 -- an ancestor of current master ( trixie )
issues-ping-reword -- ancestor of current master ( trixie )
bazel-992113 --- an ancestor of bullseye
buster-startup -- this is an ancestor of stretch (despite the name!)
1033065-i386-baseline - this is an ancestor of bookworm
The are dangling branches, where the content was merged by hand/not as
a merge commit:
rabbitmq -- looks like this was improved and became commit d1185415
(an ancestor of master (trixie))
rc-bugs -- i believe this was merged (with other changes) as 790781cd
(which is an ancestor of bookworm)
release-notes-usrmerge-992116 -- this was merged as c9043b3f (only
differences are translations) which is an ancestor of bookworm
1034248-gtk4 -- content was merged as f51d813c (an ancestor of bookworm)
anarcat-master-patch-20579 -- branch has two commits which i think
were merged in at a01383d2 and 55dcffae in buster )
Perhaps someone could delete these to make the history cleaner - there
doesnt seem to be any need to retain them as the content is merged in
--- End Message ---
--- Begin Message ---
On Mon, Jun 23, 2025 at 01:09:36PM +0100, Richard Lewis wrote:
> The release-notes repository has accumulated some old branches that
> could be deleted:
..
> Perhaps someone could delete these to make the history cleaner - there
> doesnt seem to be any need to retain them as the content is merged in
Done.
--- End Message ---
Reply to: