From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] culling the catalyst repo branches
Date: Mon, 5 Oct 2015 22:25:28 -0400 [thread overview]
Message-ID: <56133118.2050205@gentoo.org> (raw)
Hi everyone,
Currently the catalyst git repo at
http://gitweb.gentoo.org/proj/catalyst.git has the following branches:
remotes/origin/2.X
remotes/origin/3.0
remotes/origin/HEAD -> origin/master
remotes/origin/catalyst_2
remotes/origin/catalyst_3
remotes/origin/master
remotes/origin/pending
remotes/origin/rewrite-on-master
remotes/origin/tar-volume-label
as obtained by `git branch -a`. This is a bit of a mess. After
discussions in freenode/#gentoo-releng, we've come up with the following
2.X - legacy branch. Releases are coming from this branch but that will
end soon.
3.0 - development branch for dol-sen only.
master - development branch were we should focus our contributions
catalyst_2 - dead and should be nuked
catalyst_3 - dead and should be nuked
pending - has some development work in it.
write-on-master - no idea
tar-volume-label - no idea
Okay time to do some cleanup. I want to nuke the catalyst_2 and
catalyst_3 branches. dol-sen is going to take care of pending and 3.0.
I have no idea what write-on-master and tar-volume-label are so my
feeling is to nuke those too unless someone speaks up and said, wait NO!
Any comments before I act. I'll wait about a week.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
next reply other threads:[~2015-10-06 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 2:25 Anthony G. Basile [this message]
2015-10-06 2:36 ` [gentoo-catalyst] culling the catalyst repo branches Mike Frysinger
2015-10-06 2:46 ` Anthony G. Basile
2015-10-06 3:13 ` Anthony G. Basile
2015-10-06 3:19 ` Mike Frysinger
2015-10-08 0:11 ` Anthony G. Basile
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56133118.2050205@gentoo.org \
--to=blueness@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox