On Sun, Jul 17, 2011 at 4:54 AM, Ulrich Spörlein <uqs_at_spoerlein.net> wrote: ... >> Having a project adopted way of sharing work in progress will be a step >> forward. Yes, I'm aware of perforce, it's to hard to use and wasn't >> designed to share and test ideas. I think guthub can be a very good >> candidate (but AFAIK it won't allow hosting of FreeBSD repo for not paid >> accounts). I'm not suggesting switching to git as VCS, but using github >> UI for communication and tracking not yet commited or work in progress >> changes. In ideal world developers will merge patches from each other >> increasing chance of a good code to survive and get commited later. >> Currently we have patches hosted at people.freebsd.org, as attachments >> on maillists and PRs -- almost all stale or outdated. Key difference of >> github is that original patch author will be aware of you using it, >> potentially updating and improving it. Others can continue supporting >> the patch if original author abandons it, etc. Sending patches is too >> complicated and counterproductive comparing to github. > > Yes, I fully agree, that's why https://github.com/freebsd/freebsd-head > exists today, but hasn't been advertised yet (I need to write > documentation and can't force myself to do it :( > > Feel free to start using it! Together with the git-svn metadata that you > can grab from repos.freebsd.your.org it makes a solid platform for > working on FreeBSD code. +1 for git. There's also git://gitorious.org/freebsd/freebsd.git which mirrors head and stable/releng/release branches. --ArtemReceived on Sun Jul 17 2011 - 15:00:44 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:15 UTC