From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] culling the catalyst repo branches
Date: Wed, 7 Oct 2015 20:11:01 -0400 [thread overview]
Message-ID: <5615B495.7060100@gentoo.org> (raw)
In-Reply-To: <20151006031902.GG6518@vapier.lan>
On 10/5/15 11:19 PM, Mike Frysinger wrote:
> On 05 Oct 2015 22:46, Anthony G. Basile wrote:
>> On 10/5/15 10:36 PM, Mike Frysinger wrote:
>>> On 05 Oct 2015 22:25, Anthony G. Basile wrote:
>>>> 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!
>>> rather than delete branches (and thus history), how about we move them to
>>> a "old/" or "dead/" namespace ? then it'd be:
>>> refs/heads/
>>> |-- 2.x
>>> |-- 3.0
>>> |-- master
>>> `-- old
>>> |-- catalyst_2
>>> |-- catalyst_3
>>> |-- rewrite-on-master
>>> `-- tar-volume-label
>> yeah even better, except i'm not sure how to do nested branches like
>> that. i'll google it.
> that part is simple :). there's nothing special with refs.
>
> create a copy first:
> $ git push origin -n remotes/origin/catalyst_2:refs/heads/old/catalyst_2
> To git+ssh://git@git.gentoo.org/proj/catalyst.git
> * [new branch] origin/catalyst_2 -> old/catalyst_2
>
> then delete the old one:
> $ git push origin -n :refs/heads/catalyst_2
> To git+ssh://git@git.gentoo.org/proj/catalyst.git
> - [deleted] catalyst_2
> -mike
All done.
--
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
prev parent reply other threads:[~2015-10-08 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 2:25 [gentoo-catalyst] culling the catalyst repo branches Anthony G. Basile
2015-10-06 2:36 ` 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 [this message]
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=5615B495.7060100@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