durham_meta

5 ms·

1.
by durham_meta 4y ago
Yea, that's on our list to fix. The homebrew packaging was the last package to be done, and we were busy tidying up other things in the lead up to launch.
2.
by durham_meta 4y ago
Because we haven't released the server yet, the open source client currently only really supports git right now, so sl init --git is the only way to init a local repo for now. Perhaps we could make that message clearer. I'll take
3.
by durham_meta 4y ago
You could personally clone a git repo with Sapling and no one would know the difference. When using Sapling with a git repo, clone, push, and pull all use the actual git binary under the hood, so the server just sees git speaking to it.
4.
by durham_meta 4y ago
You cannot just start using sl in a git repo. You need to make a Sapling clone of it. But you can make a Sapling clone of your local git repository, so you don't have to clone from the server again and you would get all your local work
5.
by durham_meta 4y ago
Sorry! 'one day' is the best I can do for now. We'd love to do it sooner, just gotta find the time. We think, and many of our internal users agree, that the UX alone is a worth while upgrade. Since the majority of Git repos d
6.
by durham_meta 4y ago
Technically the mercurial pre and post hooks are mostly still there, but I'm not certain we want to support them long term. The existing hook design has some problems. I'd be curious about your use case, since we don't actual
7.
by durham_meta 4y ago
Unfortunately we can't really talk too much about that at this point. I can say a lot of effort has gone in on the server side to optimize commit throughput though. One example we mention in the blog post is that when you push, it does
8.
by durham_meta 4y ago
Unfortunately you can't use Sapling with Mercurial repositories. There are too many differences at this point. This does not use hg-git under the hood. Sapling's internal structure differs from Mercurial in substantial ways, and w
9.
by durham_meta 4y ago
We're somewhat limited by what version of clap is available in our internal monorepo. We try to keep things reasonably up-to-date though, so I'm sure we'll upgrade at some point. I believe we actually only use clap for some
10.
by durham_meta 4y ago
You should be able to `sl clone ...` your git repo into a Sapling clone and use it that way, even if the repository is not on Github. I haven't personally tried whether cloning like `sl clone /path/to/some/repo` wo
11.
by durham_meta 4y ago
Unfortunately you can't run git commands directly right now, since there is no .git directory at the root of the repo. Under the hood there is a .git directory hidden away somewhere under the .sl directory, but we consider that an imp
12.
by durham_meta 4y ago
The code is available to see, but they don't necessarily build in an external environment yet and even if they did we aren't ready to support them being used externally. Hopefully we can support them one day, but for now we'
13.
by durham_meta 4y ago
Sapling originated from the Mercurial open source project, which was largely Python (at the time). To make things faster and more maintainable, we started rewriting portions of it in Rust, and going through a binding layer to interact with
14.
by durham_meta 4y ago
Good memory! Internally Eden eventually became synonymous with our virtual filesystem, so we decided it was better to choose a new name to avoid that confusion.
15.
by durham_meta 4y ago
Hi Hacker News! Author of the Sapling blog post here. I'm happy to answer any questions you might have.