Re: FYI: github
Its fine by me; we could push squid3 up as well using bzr-git, if folk are interested. -Rob
Re: FYI: github
Absolutely. The only reason I didn't do it is that I'm not as familiar with bazaar... Cheers, On 16/08/2010, at 8:22 AM, Robert Collins wrote: Its fine by me; we could push squid3 up as well using bzr-git, if folk are interested. -Rob -- Mark Nottingham m...@yahoo-inc.com
Re: FYI: github
On Sun, 15 Aug 2010 17:11:31 -0700, Mark Nottingham m...@yahoo-inc.com wrote: Absolutely. The only reason I didn't do it is that I'm not as familiar with bazaar... Cheers, On 16/08/2010, at 8:22 AM, Robert Collins wrote: Its fine by me; we could push squid3 up as well using bzr-git, if folk are interested. -Rob -- Mark Nottingham m...@yahoo-inc.com I think we need some more wiki updates to the VCS area, indicating where all the read-only alternative-VCS mirrors are with how to access them. Amos
Re: FYI: github
fre 2010-08-13 klockan 18:54 -0500 skrev Mark Nottingham: P.S., if any other squid-dev people are on github, we can add you to the group, FWIW, although like I said, this is read-only... I have a github account. hno as mostly everywhere else. But I see you already noticed that. Regards Henrik
Re: FYI: github
Yep. I didn't hit the 'publicise' button to make that public, tho; figured I'd leave that to you. Cheers, On 16/08/2010, at 12:52 PM, Henrik Nordström wrote: fre 2010-08-13 klockan 18:54 -0500 skrev Mark Nottingham: P.S., if any other squid-dev people are on github, we can add you to the group, FWIW, although like I said, this is read-only... I have a github account. hno as mostly everywhere else. But I see you already noticed that. Regards Henrik -- Mark Nottingham m...@yahoo-inc.com
FYI: github
I've noticed a few people creating Squid2 trees using git. The problem with this is that when they do so, they get a snapshot of squid at that time. To make it easier for them to track HEAD, I've created a mirror of the squid2 source on github: http://github.com/squid-cache/squid2 This is semi-automatically updated from HEAD (and will be automatic once I get my cron jobs in order). Now, people can fork that project and more easily integrate updates. Note that it's read-only; i.e., patches won't be accepted there (although it should be easy to take patches from a forked version back to CVS). I asked on IRC if anyone minded this, and no one seemed to, but if it's a big problem I'm happy to delete the repository. Some may be interested in this visualisation (scroll to the right): http://github.com/squid-cache/squid2/graphs/impact Cheers, P.S., if any other squid-dev people are on github, we can add you to the group, FWIW, although like I said, this is read-only... -- Mark Nottingham m...@yahoo-inc.com
