| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Husky Git repo? |
Hello RJ! 26 Jan 14 03:50, RJ Clay wrote to Gerrit Kuehn: GK>> I have it working with Husky now, but it was not that easy because GK>> cvsps turned out to be incompatible with the way Husky is plit into GK>> cvs modules. RC> One reason I hadn't gotten to it yet mysesf... Did you end up with RC> one repo RC> with multiple branches, or multiple repos? I went for multiple repos, having one repo per module. GK>> I had to do some scripting to get around this. RC> And is that publically available somewhere? SF? or Github, RC> perhaps? No, I just scribbled together some lines for me here. But I'm happy to share this in case anybody else might be interested. You need to have git with cvs support (cvsps), obviously. My cvs checkout resides in ~/husky. I used this to get the module names to import: ---* Origin: And still they come and go (2:240/12) SEEN-BY: 3/0 633/267 280 640/384 712/0 550 848 @PATH: 240/12 1120 280/5003 464 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.