image/jpeg
Error showing notice: File not found in filesystem.
@normandy @moonman I actually haven't tried gogs, maybe I'll see if it runs with the main site software better than gitlab does. I'd compartmentalize these into their own VMs but I'm outta IP4s unless I buy some more, and moneys tight until I'm done rewiring and renovating the basement.
@maiyannah @moonman Never really used CVS, but I did play with Subversion which is somewhat similar.
@normandy @moonman SVN and GIT are actually compatible. Not sure why they never did with CVS, the system is easy to import into other systems (though you can get GIT compatibility by proxy I guess since you can import CVS into SVN using most client apps.)
@moonman @normandy The major difference in my experience is more the front end than the backend, though I notice git repos tend to grow larger than CVS ones over a length of time. The only major backend difference is CVS does not keep local copies of branches on a non-master repo, just the working branch. Though to be fair, many clients like TortoiseCVS have workarounds built in for this. I do find the backend of GIT seems much quicker performance wise on lower-end mmachines, such as when I use my laptop to code from bed, though, and that's noteworthy.
As to the front end differences, I can't say I prefer GIT in that regard. The naming system is completely counterintuitive and conflict resolution ends up running into all kinds of problems such as that weird postActiv thing we ran into, which was a result of GITs automerge going autoderp when importing changes from upstream Mikael had made in GNU social.
@moonman @normandy That said, there's a lot to be said for using the thing everyone else is, in this context, since CVS, SVN, GIT, et al, are all ultimately meant to allow code collaboration.
@maiyannah @normandy I will only ever use DVCS again if I can help it. I was actually surprised the other day when I had to move a subversion repo and I forgot that my local copy wasn't as good as the remote repo.
@maiyannah @moonman @normandy If I ever run gitlab, it will be inside #sandstorm . It's there!
@maiyannah @moonman @normandy I do see the point if RCS. But CVS is just a good idea taken too far. git is a good remake of the whole idea.
@maiyannah @moonman @normandy I'll keep pushing #sandstorm even though I've never used it myself, because it looks like such a good idea.
@maiyannah @moonman @normandy #gogs is on #sandstorm. :-)
@maiyannah @normandy @moonman I'm using gogs on my server, it's super-simple to set up and works really well. If you don't need the more exotic features of gitlab, I'd recommend it.
@maiyannah @moonman @normandy git and svn are closer semantically than svn and CVS, because CVS versioning is per-file, not per-commit.
@maiyannah @moonman @normandy There are git-CVS bridges, but they are all kludges. Big gang migration is the only sane way to go.
@maiyannah @moonman @normandy The .git directory is generally smaller than the checked-out work tree, even after a decade of commits.
@moonman @maiyannah @normandy svk used to be my life-saver on svn. Until I discovered what a great svn client bzr is.
@normandy @moonman Yes. Git itself is decentralized. The way most people use it isn't. Linus uses it with a federated social network! (mail)
@normandy @moonman @maiyannah They have a #mattermost instance too? Cool.
How are they financed? Donations?
@clacke @moonman @maiyannah Yeah it seems to be financed by donations.
@clacke @moonman @normandy IIRC they had a crowdfunding thing. Not sure how they plan to finance it when that money runs out, donations probably.
@normandy @moonman @maiyannah Run by this group https://opengem.org/projects/ , which also runs 8chan archives. Unexpected turn!
@clacke @normandy @maiyannah i've heard good things about bzr but i'm a mercurial fan. best parts of git.
@normandy @moonman @maiyannah They're looking into premium accounts across their services: http://qttr.at/1i33 (blog.opengem.org)
@normandy @moonman Using it in a decentralized manner requires remote login provisions on all users' machines, which is a terrible idea on the open Internet.
@takeshitakenji @moonman @normandy No it doesn't, you're thinking too small. Like I said, a mailing list with patches is federated git use.
@takeshitakenji @moonman @normandy Most ways of sharing global state decntralized probably end up using some form of DHT and/or blockchain.
@clacke @normandy @takeshitakenji @moonman I wish git had integrated bugtracking like http://fossil-scm.org/index.html/doc/trunk/www/index.wiki.
@moonman @maiyannah @normandy The best part of bzr is how great it does svn. I do use git w/ multi worktrees tho, which is pretty bzr-esque.
@lambadalambda @moonman @takeshitakenji @normandy Yes. http://dist-bugs.branchable.com/software/ shows several failed or dormant attempts.
@lambadalambda @moonman @takeshitakenji @normandy I want a p2p distributed git/issues/wiki hosting network with a federated web frontend.
@clacke @normandy @takeshitakenji @moonman except for git, this sounds like fossil :)
@lambadalambda @moonman @takeshitakenji @normandy Indeed. I believe any mainstream success must include git.
@lambadalambda @moonman @takeshitakenji @normandy Also, Fossil lacks the truly automatic distribution. Sync setup is explicit and manual.
@lambadalambda @moonman @takeshitakenji @normandy Autosync uses a public, central server. http://qttr.at/1i55 (fossil-scm.org)
@clacke @moonman @normandy Seriously? A mailing list with patches? Isn't the whole point of SCM to remove that obsolete means of disseminating changes?
@moonman @normandy @clacke Next up, you're going to tell me that we should be sending complete copies of source code inside compressed archives through e-mail instead of using SCM at all.
@takeshitakenji What do you think `git format-patch` and `git am` are for? Git was written by a guy whose primary project workflow is e-mailed patches. The repository itself is what keeps track of changes and the reasoning.
The point of a version control system is to have a working copy of a given project and its entire history, on the off chance that a decision made 10 commits ago is bad and needs to be reversed.
A distributed one simply gets rid of the primary weakness of SVN and CVS; *anyone* who clones the repo can work on it anywhere, and then submit patches (via e-mail or other means) to others.
Under this model, the best way to get your changes into "the main project" is to talk to the ones who control what's considered the canonical repository and convince them to add it to their repo. Once they do, others pull from them and now everyone has your patch.
If you don't mind me asking, how do you personally use git?
Christmas Personified as a Catgirl
clacke
Normandy
All Roland's Microblog content and data are available under the 