Live data from Hacker News

Gitless: an experimental version control system built on top of Git

people.csail.mit.edu

1–10 of 48 posts

Re: Gitless: an experimental version control system built on top of Git

#4
post #2

I don't understand what it is supposed to do. > Check out the documentation section to get started. > Documentation: TODO.

There must be a dead link somewhere. If I follow the documentation link in the top menu, I get to docs.

Re: Gitless: an experimental version control system built on top of Git

#5
post #2

I don't understand what it is supposed to do. > Check out the documentation section to get started. > Documentation: TODO.

I see the documentation.

Seems to be Git without Commits - kind of. It seems to be better described here:

> Unlike traditional version control systems (such as CVS and Subversion), Gitless is distributed. Rather than having a single, centralized repository, each user has her own repository that is synchronized with other repositories.

Re: Gitless: an experimental version control system built on top of Git

#8
post #2

I don't understand what it is supposed to do. > Check out the documentation section to get started. > Documentation: TODO.

I see the documentation. Seems to be Git without Commits - kind of. It seems to be better described here: > Unlike traditional version control systems (such as CVS and Subversion), Gitless is distributed. Rather than having a single, centralized repository, each user has her own repository that is synchronized with other repositories.

That quote can be applied verbatim (but for s/Gitless/Git) to Git itself.

Re: Gitless: an experimental version control system built on top of Git

#9

So... what advantages does this provide over straight Git? Reading the docs, it doesn't appear to abstract over Git at all.

From what I can see: easier control over tracked/untracked status of files; no stage (might be considered a disadvantage, though I'll wager a good interactive commit feature would render a stage unnecessary), automatically commit everything by default, much simpler concept of what a branch is and isn't; no fetch at all, just merge.

I like this experiment quite a lot. It's clearly very incomplete and lacking of features, but I feel that it gets the basic concepts more right than Git does. For example, the idea that merging from a local branch or merging from a remote branch is the same, is very nice and simple. Sure, it's not like 'git pull' vs 'git merge' is a lot more work, but still, I'd like to not be bothered by the difference.

There's a whole bunch of edge cases still missing here, I fear, but I really like where this is heading. Would use.

Re: Gitless: an experimental version control system built on top of Git

#10
A nice project: Git is a wonderful version control system, but the git cli (the porcelain) definitely has some annoyances. I think submodules, for example, are completely broken at the CLI level.

I don't think this project necessarily goes far enough though; the biggest change I saw was getting rid of the staging area. Whether or not that's a good idea, I was hoping for crazier ideas!

For example, how about something that is more aware of github, where my github branches auto-update, and works nicely with forks, pull-requests and issues. The git-review integration for gerrit is interesting along those lines: https://pypi.python.org/pypi/git-review

Post reply on HN