martinvonz

5 ms·

31.
by martinvonz 1y ago
Thanks for the detailed comment. My target audience were the people at the conference, who are mostly long-term jj users. The topic was "Jujutsu at Google: Architecture and future plans", i.e. explaining how it works and what our
32.
by martinvonz 1y ago
Thanks! The presentation was mainly for the audience that was present at the conference, which was mainly people who have used jj for a relatively long time, so I think part of the problem is just a mismatch between audiences there and on Y
33.
by martinvonz 1y ago
Putting less details on the slides is something very actionable. Thanks. > Also, present things that you are passionate about if you want to make people care about your presentation. Haha, this topic is something I'm very passionate
34.
by martinvonz 1y ago
Thanks for the link. I went through it but I'm not sure what it's telling me to change. Can you elaborate? If it's "be more engaging", i think is unfortunately going to be hard to improve because this is just how i
35.
by martinvonz 1y ago
That won't update sibling branches
36.
by martinvonz 1y ago
> jj does this for performance reasons. They don't want to perform a full checkout for every rebase action. It's true that `jj fix` can be faster by not touching the working copy, but we also want a `jj run` command for the lin
37.
by martinvonz 1y ago
j2kun seems to be a googler so I don't think so, but it's true that Facebook also went with Mercurial. I suspect it was for similar reasons.
38.
by martinvonz 1y ago
Yes, that's correct. Another reason was that Mercurial is easier to customize because it's written in Python so we could sometimes just replace whatever we needed without needing much changes from Mercurial itself. Yet another rea
39.
by martinvonz 1y ago
I think you misunderstood. I didn't ask for their name. Luckily the author didn't seem to misunderstand. As for information about me, you can search the internet for my username. Let me know if you don't find anything and I c
40.
by martinvonz 1y ago
Thanks for working on this project! It was mentioned on the JJ Discord server that there doesn't seem to be any information available about who you are. Especially since the project seems to be closed-source, perhaps you could share so
41.
by martinvonz 1y ago
Do you mean if jj has separate author and committer timestamps? Yes, we simply followed Git there. I didn't really question it. There has been some discussion about simplifying it to just one timestamp, however. You can probably find t
42.
by martinvonz 1y ago
We don't have --committer-date-is-author-date. I don't think we've had a single request for it until now. That flag seems a bit weird, though. Wouldn't you want to keep whatever the committer date already was? Why would
43.
by martinvonz 1y ago
Ah, I see what you're saying now. Thanks for explaining. I agree with you in principle. My impression from our Discord server is that quite many JJ users actually are Git experts who have been creating clean commits for years. I'm
44.
by martinvonz 1y ago
FWIW, Drew DeVault wrote such an article but he later took it down (in protest of the Google CLA, I think). You can probably still find it somewhere. > Since you're a git expert, you understand the underlying mechanics of your tool
45.
by martinvonz 1y ago
> The impression I get from these posts, is that it would have been doable with similar effort in Git, but they just never bothered. I don't think it would have been doable. I hear this question/comment sometimes. I sent https
46.
by martinvonz 1y ago
That's correct. It's only on our roadmap so far ( https://jj-vcs.github.io/jj/latest/roadmap/#better-support-f... ). We have also talked about doing something similar for tree objects in order to bett
47.
by martinvonz 1y ago
I don't know why you think jj makes you produce many little commits. Are you thinking about the automatic snapshotting of the working copy? That amends (replaces) your previous commit, so you won't end up with a long chain of comm
48.
by martinvonz 1y ago
Yes, that's correct. It's also correct to say that you don't "need" the Git porcelain commands because it's perfectly doable using Git plumbing :)
49.
by martinvonz 1y ago
Yes, the result is (almost) just regular Git commits, so there isn't anything jj can do that Git cannot do. It's just often a lot easier to do it with jj. A lot of jj users are former Git power users. If all you do you use is `git
50.
by martinvonz 1y ago
In some sense, every jj command does more than any single git command because they implicitly amend the working-copy commit and rebase any descendants on top. Another example is `jj rebase -d main`. It may look very similar to `git rebase
51.
by martinvonz 1y ago
I'm not sure if you meant "how" or "why". As for "how", it's done by rebasing 'u' onto 's' and then rebasing 't' and 'v' onto the rebased 'u'. As for
52.
by martinvonz 2y ago
Yes, it was to avoid ambiguity between the two kinds of IDs. See https://github.com/jj-vcs/jj/pull/1238 (see the individual commits).
53.
by martinvonz 2y ago
We have database-backed storage backends for Jujutsu at Google. There's no Git involved there. So I think it's wrong to say that it's a wrapper for Git. Even when using the Git backend, it's only commits and lower-level
54.
by martinvonz 2y ago
I'm not sunshowers, but I think the point isn't the exact number or a way of measuring it. For example, the reason I prefer to write Rust over C++ is not that I have measured it to be 2.6X faster for me to work with. My interpreta
55.
by martinvonz 2y ago
We were actually talking about this for quite a while on Discord yesterday. The duality is visible to the user in jj as least as much as it is in git. Some command arguments treat commits as snapshots (e.g. `jj restore --from/--into`,
56.
by martinvonz 2y ago
It's hard to find that information because neither git nor jj report usage information to a central place. The best I've been able to find is number of Homebrew installs, which says ~1.2k 30-day install for jj and ~162k for git, s
57.
by martinvonz 2y ago
I apologize if my sibling comment sounded harsh. I think you were saying that jj could be implemented as some Git aliases. Given the information available in this thread, that might seem reasonable. I didn't realize that this thread di
58.
by martinvonz 2y ago
I think you misunderstood. Did you see the list of features? My example is not the only thing jj does.
59.
by martinvonz 2y ago
Have you tried asking your colleagues? What did they say?
60.
by martinvonz 2y ago
To move the changes in file `foo` in the working copy into a past commit `X`: `git commit --fixup=X foo; git stash; git rebase -i X^; git stash pop` `jj squash --into X foo`

More ›