Live data from Hacker News

Fossil SCM

fossil-scm.org

11–20 of 147 posts

Re: Fossil SCM

#11
post #3

No/manual rebase sounds awful

Genuinely curious: Why do you need rebasing?

I'm mostly a mercurial person, where doing a rebase is highly discouraged and nontrivial. After all these years on mercurial, I've never found a need to do it. Why is it so popular amongst git users?

Re: Fossil SCM

#12
post #2

GitLab contributors, please take note. Fossil's UI is very fast and the navigation is intuitive and discoverable. I know it's on the roadmap, but it is so often an afterthought.

I couldn't find any screenshots on the site, can you share any?

Re: Fossil SCM

#15
post #11
post #3

No/manual rebase sounds awful

Genuinely curious: Why do you need rebasing? I'm mostly a mercurial person, where doing a rebase is highly discouraged and nontrivial. After all these years on mercurial, I've never found a need to do it. Why is it so popular amongst git users?

Usually as a way to ensure a working branch stays up to date with master/another branch, so there aren't merge conflicts. Or if there are merge conflicts, to resolve them.

Re: Fossil SCM

#17
post #12
post #2

GitLab contributors, please take note. Fossil's UI is very fast and the navigation is intuitive and discoverable. I know it's on the roadmap, but it is so often an afterthought.

I couldn't find any screenshots on the site, can you share any?

Just click the link above, the entire site is Fossils interface.

Re: Fossil SCM

#18
post #11
post #3

No/manual rebase sounds awful

Genuinely curious: Why do you need rebasing? I'm mostly a mercurial person, where doing a rebase is highly discouraged and nontrivial. After all these years on mercurial, I've never found a need to do it. Why is it so popular amongst git users?

Rebasing gives you a linear history instead of the diamonds non-rebased branching and merging gives you. I mean, that's the technical reason, anyway.

Re: Fossil SCM

#19
post #10
post #5

Fossil is the SCM I always wish I were using, but for the benefit of external collaborators, I stick with Git and GitLab (previously, GitHub). Fossil is a lovely, small piece of software that does exactly what I want in a nice and simple way. It's fast and uses SQLite for everything, making it easy to programmatically extend it and munge its internal data.

SQLite usage makes me wonder how will it behave over time with millions of commits. Also makes me wonder how will it handle distribution.

Indeed, what are the consequences of that choice, vs. git and hg?

Re: Fossil SCM

#20
post #12
post #2

GitLab contributors, please take note. Fossil's UI is very fast and the navigation is intuitive and discoverable. I know it's on the roadmap, but it is so often an afterthought.

I couldn't find any screenshots on the site, can you share any?

I believe the site itself is running an instance of Fossil?
Post reply on HN