[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30770 [Internal Services/Tor Sysadmin Team]: consider alternatives to the puppet mono-repo
#30770: consider alternatives to the puppet mono-repo
-------------------------------------------------+---------------------
Reporter: anarcat | Owner: tpa
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Tor Sysadmin Team | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: #29387 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+---------------------
Comment (by anarcat):
i just tried subrepo for the [https://gitlab.com/anarcat/puppet-lnav/ lnav
module] and i gotta say it's pretty damn simple. all i did was:
{{{
git subrepo init modules/lnav/ -r https://gitlab.com/anarcat/puppet-
lnav.git
git subrepo push modules/lnav -r git@xxxxxxxxxx:anarcat/puppet-lnav.git
}}}
and voilà: the remote repo has the files ''complete with the full history
of the changes in that subdirectory''! that's a killer feature, i think.
the two different `-r` arguments are there so that people that clone the
monorepo get the publicly-readable URL they can pull from in the future.
the only disadvantage of subrepo i can think of is that subdirectory isn't
a real git repository locally: it's just a subdir.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30770#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs