3 ms·
> No, that's not something I've even started thinking about. I'll have to read up on how it works in Git first. Patches welcome, though :) I opened an issue an
by mdaniel 5y ago
> No, that's not something I've even started thinking about. I'll have to read up on how it works in Git first. Patches welcome, though :)
I opened an issue and provided links to the docs, and a link to the current way that git implements it: https://github.com/martinvonz/jj/issues/58 https://github.com/martinvonz/jj/issues/58
As I was trying to find the correct command in jj for where to add the new argument, I realized that this may not play nice-nice with jj's commit-everything model, so I'm actually prepared for the issue to be closed WONTFIX :-)
As for the patches welcome part, I notice that the Google CLA bot is on your repo. While I do have the CLA signed for my Gmail address, it seemed like some major tomfoolery to try and add my current github email address (and the one which backs my GPG key, to bring this full circle!) to the existing CLA process. Do you intend to keep that CLA mechanism in place, or was it just an oversight?
- martinvonz 5y ago> I realized that this may not play nice-nice with jj's commit-everything model Yes, I suppose you might not want to sign every working copy commit, but as you noted on the issue, it would probably make sense on `jj close/commit` (aliases). > Do you intend to keep that CLA mechanism in place I started working on this project internally and then open-sourced it. I don't think I'm allowed to remove the CLA bot. I understand that it's annoying :(