schacon

12 ms·

1.
by schacon 29d ago
Well, there are a couple of problems here, if you are interested in an actual answer. The first is that update-index only works on worktree files, so you need to be actually modifying file contents on disk and then essentially running `hash
2.
by schacon 29d ago
In case you're curious if _you_ can run `git history split`, the answer is almost certainly no, unless you manually installed the newest release of Git within the last 3 months. `git history` was introduced as an experimental command l
3.
by schacon 29d ago
Not only this, but it's not super simple to update to the newest version anymore. I actually tried this today and I'm on `2.50.1 (Apple Git-155)`. It turns out I don't actually know how to update that. `brew install git` does
4.
by schacon 29d ago
Not sure if this is written by an AI, but I'll engage, because it's a bit misleading. The new `git history` command can take three verbs - fixup, reword and split. While interactive rebasing can do fixup and rewording relatively e
5.
Deep dive into Git's wire protocol(scottchacon.com)
3 points by schacon 2mo ago|0 comments
6.
Keppsake – automatic save points for your AI projects(keepsake.sh)
2 points by schacon 2mo ago|0 comments
7.
by schacon 3mo ago
In California, it's capped at a knowable amount when you buy the home and pegged at the sale price. You know what it is and what it always will be when the transaction happens. The people whom have owned a house now worth a million for
8.
by schacon 3mo ago
Love it. In fact, we should have expanded it to be a "millionaire tax" where everyone who has a home worth more than $1M needs to pay a one time $50k+ tax to the highly efficient state government. I'm sure they can easily fig
9.
by schacon 3mo ago
Relicensing under any other license, including the LGPL, is exactly the same thing. Either the reimplementation copies protected expression, in which case it would be required to be GPL-2.0-only, or it does not, in which case we can choose
10.
by schacon 3mo ago
> Would you be happy for someone to do the same with the GitButler source code? Honestly, that would be pretty awesome. We would be flattered.
11.
by schacon 3mo ago
Nice, I haven't dug into this yet. If we can get this usable, it would be pretty cool to have a small lib or a series of much smaller, directed libs that can be used by simpler interfaces and you can just compose the parts you need.
12.
by schacon 3mo ago
Not yet. I have a PR with a WASM experiment based on an earlier build, but it's not integrated. It's on my list of things to try. I _did_ get it working for some things, so it's clearly possible, but I need to put some more e
13.
by schacon 3mo ago
Well, there's lots of really interesting opinions here from a lot of armchair lawyers. To clarify, my stance on this is that the reimplementation did not copy protected expressions (Jplag reports less than 1.8% max similarity between t
14.
by schacon 3mo ago
GitButler's source code is available, so we're not asking you to trust us much at all. https://github.com/gitbutlerapp/gitbutler
15.
by schacon 3mo ago
A feature complete, reentrant, linkable library. Reading the article often helps with questions like this.
16.
by schacon 3mo ago
As mentioned, we also work on the Gitoxide project and Byron is a member of our team. We are well aware of all large community efforts and we're also cohosting the Git Merge conference this year. There is a recent effort to vibe-loop m
17.
by schacon 3mo ago
I think Byron (Gix author/maintainer) is one of the most excited people about the Grit project. Gitoxide is great and we will continue to push it forward. Grit is an orthogonal project. Perhaps we can use one in the other or maybe Grit
18.
by schacon 3mo ago
I see it differently. I look at it as if I had written this code myself, using this same approach. Look at the docs, look at the tests, look at the source, implement something that is interactively compatible but a very different approach.
19.
by schacon 3mo ago
To be clear, I 100% did not make libgit. I did help the libgit2 project get off the ground.
20.
by schacon 3mo ago
I'm assuming you didn't read the article, since I'm pretty sure I covered all of this, but I'm happy to respond. Don't bother. It's probably not for you. It's slower, more obtuse, more bloated, less capabl
21.
by schacon 3mo ago
We're choosing a license that is usable by the entire community. Our goal is a linkable library, which makes GPL impossible. If we had chosen to go with LGPL or GPL with linking exception (like libgit2), it would have the same issue of
22.
by schacon 3mo ago
Gitoxide is also developed primarily by Byron, who also is part of the GitButler team. We're pushing both projects forward.
23.
by schacon 3mo ago
I'm happy to take contributions if you want to throw some tokens at it. Bug reports would be amazing, since I haven't tested it for real very much (enough to know you can do basics). I want to get it to the point where we can repl
24.
by schacon 3mo ago
I started the project as Gust, but felt like Grit was such a better name. I asked Tom if I could boot the name back up again because I always liked it and he said it was fine. Also, I worked on the Ruby Grit pretty extensively during the ea
25.
by schacon 3mo ago
I would not use this except to help us test it if interested. I'm announcing it because it's interesting and a milestone in the breadth of test coverage it can pass. It almost certainly cheated on a bunch of those tests and is not
26.
by schacon 3mo ago
libgit.a isn't reentrant. It will call `die()` on many errors. If you link to it in a long running binary, it will kill your process on error. Libgit2 is meant to address this and I was heavily involved in the development of that proje
27.
by schacon 3mo ago
My intent with this project is not to replace Git in any way. I don't care about the CLI part of this project. The point is to provide a feature-complete reentrant linkable library. Even if it's an ugly and slow one, this is still
28.
by schacon 3mo ago
I would also be interested. I haven't dug into this at all yet, nor have I tried to optimize the size (or really, anything else). However, the library part will be less than half of this - a lot of code is spent on the CLI specific stu
29.
by schacon 3mo ago
It's not for Rust, it's for Library. Well, it's sort of for Rust. GitButler is written in Rust and Jujutsu is written in Rust and we're both depending on fork/exec'ing to an unknown Git binary with no linkable
30.
by schacon 3mo ago
I addressed this in the post, but Git has no linkable library and never has. If you want to do even something small, you need to fork/exec a process and communicate with it via stdin/out. Or completely reimplement it and all of th

More ›