A better merge workflow with Jujutsu • Hacker News Board

Re: A better merge workflow with Jujutsu

#91

Post by aseipp » Thu, Jul 04, 2024, 4:47 AM UTC

technojamin wrote: post #83

Jujutsu seems really cool, and I love that I can use it in a Git repository alongside other contributors that don't. It seems like a lot of logging features from Git aren't present, though. Besides the mentioned lack of blame functionality[1], things like path filtering (`git log -- `), file-following with rename detection (`git log --follow -- `), pickaxe (`git log -S `), and range evolution (`git log -L , : `) are…

Following up late to this, but, broadly speaking: we mostly just haven't added these features because users haven't asked for them and we haven't otherwise gotten around to it. That's basically it. They would all be useful and/or welcome (assuming we were happy with the implementation.)

(We also don't want to necessarily just straight-up copy raw implementations, but improve on them where we can. But most of the asks here are pretty straightforward, I admit.)

> path filtering (`git log -- `)

This already works today with `jj log`.

Re: A better merge workflow with Jujutsu

#92

Post by technojamin » Fri, Jul 05, 2024, 3:15 PM UTC

aseipp wrote: post #91

technojamin wrote: post #83

Jujutsu seems really cool, and I love that I can use it in a Git repository alongside other contributors that don't. It seems like a lot of logging features from Git aren't present, though. Besides the mentioned lack of blame functionality[1], things like path filtering (`git log -- `), file-following with rename detection (`git log --follow -- `), pickaxe (`git log -S `), and range evolution (`git log -L , : `) are…

Following up late to this, but, broadly speaking: we mostly just haven't added these features because users haven't asked for them and we haven't otherwise gotten around to it. That's basically it. They would all be useful and/or welcome (assuming we were happy with the implementation.) (We also don't want to necessarily just straight-up copy raw implementations, but improve on them where we can. But most of the asks…

I completely missed the `` argument despite being the first thing documented under `jj log`. That's definitely the most critical feature out of my list, thank you for pointing that out!

Also, it's great to hear that you're willing to accept contributions for those features. If/when Jujutsu gains critical mass, I imagine that someone will end up contributing these features.

Regarding rename detection, it seems like that is actively being worked on, which is really encouraging! https://github.com/martinvonz/jj/pull/3574

Re: A better merge workflow with Jujutsu

#93

Post by g-b-r » Fri, Jul 05, 2024, 10:17 PM UTC

jeltz wrote: post #76

g-b-r wrote: post #43

Earlier quoted context omitted.

It's not a matter of habit but of widespread usage If you're a developer, for almost every job or open source job you'll be required to use git, but I think most people long of moving away from it

Not my experience at all. Most devs I have met in real life love git. It is certainly not perfect but it is good and way better than what came before. I would be happy if someone wrote a replacement which improved substantially upon git but if that never happens that would be fine too.

Well not my experience, but yeah let's hope that something much better replaces it soon