4 ms·

https://github.com/martinvonz/jj https://github.com/martinvonz/jj is a promising alternative which fixes many of the design mistakes of Git, but can still inter

https://github.com/martinvonz/jj https://github.com/martinvonz/jj is a promising alternative which fixes many of the design mistakes of Git, but can still interact directly with Git repositories.

jchook 5y ago
Funny that Google requires employees to say "THIS IS NOT A GOOGLE PROJECT, THIS IS MY 20% PROJECT", yet reserves the right to say "I can have this" at any point.
- oh_sigh 5y ago
  Well, Google literally paid the salary of the developer while he was developing it. This isn't even like it was something done on his personal time that Google can stake ownership in since he works there. It literally is a work product, which just happens to be not supported by Google.
- jamesmishra 5y ago
  The first one is a warranty issue. The second one is a work-for-hire-copyright-law issue.
999900000999 5y ago
Thanks this looks pretty cool. Honestly all I want is a git command that runs git commit . -m timestamp git push I probably do something like that every 20 minutes or so.
mekster 5y ago
This is the right approach. Since everyone just stepped on to use git without thinking, "Because Linux uses it", we have to endure the pain of unfriendliness of git and it's already like S3 where if you want to start any competing project, it has to be git compatible to even get started. I suppose there are SubGit, hg-git, bzr-git trying to keep their respective version control while facing git on the other end. Somehow people miss these messages and projects like Bazaar got ran over by git for no good reason. > We take great pride in making Bazaar easy to learn, easy to use and suitable for everyone, not just elite hackers. > Ease of use is a core value for Bazaar and there are many places where our focus on usability shines though. http://doc.bazaar.canonical.com/migration/en/why-switch-to-bazaar.html http://doc.bazaar.canonical.com/migration/en/why-switch-to-b... I thought people were looking for tools with this philosophy.
- theamk 5y ago
  I remember using git when everyone in my org was still on svn, using git-svn extension. I did not care who used it -- I just wanted lightweight branches with easy rebase/amend. Keeping all the extra checkouts, old copies and .diff files around was getting annoying. Today, all the VCSs offer more-or-less the same set of features (Fossil being somewhat an exception in that regard). But in the past, there were quite a lot of differences. A lot of arguments for git were very technical.

https://github.com/martinvonz/jj https://github.com/martinvonz/jj is a promising alternative which fixes many of the design mistakes of Git, but can still interact directly with Git repositories.

jchook 5y ago

Funny that Google requires employees to say "THIS IS NOT A GOOGLE PROJECT, THIS IS MY 20% PROJECT", yet reserves the right to say "I can have this" at any point.

oh_sigh 5y ago
Well, Google literally paid the salary of the developer while he was developing it. This isn't even like it was something done on his personal time that Google can stake ownership in since he works there. It literally is a work product, which just happens to be not supported by Google.
jamesmishra 5y ago
The first one is a warranty issue. The second one is a work-for-hire-copyright-law issue.

999900000999 5y ago

Thanks this looks pretty cool. Honestly all I want is a git command that runs git commit . -m timestamp git push I probably do something like that every 20 minutes or so.

mekster 5y ago

This is the right approach. Since everyone just stepped on to use git without thinking, "Because Linux uses it", we have to endure the pain of unfriendliness of git and it's already like S3 where if you want to start any competing project, it has to be git compatible to even get started. I suppose there are SubGit, hg-git, bzr-git trying to keep their respective version control while facing git on the other end. Somehow people miss these messages and projects like Bazaar got ran over by git for no good reason. > We take great pride in making Bazaar easy to learn, easy to use and suitable for everyone, not just elite hackers. > Ease of use is a core value for Bazaar and there are many places where our focus on usability shines though. http://doc.bazaar.canonical.com/migration/en/why-switch-to-bazaar.html http://doc.bazaar.canonical.com/migration/en/why-switch-to-b... I thought people were looking for tools with this philosophy.

theamk 5y ago
I remember using git when everyone in my org was still on svn, using git-svn extension. I did not care who used it -- I just wanted lightweight branches with easy rebase/amend. Keeping all the extra checkouts, old copies and .diff files around was getting annoying. Today, all the VCSs offer more-or-less the same set of features (Fossil being somewhat an exception in that regard). But in the past, there were quite a lot of differences. A lot of arguments for git were very technical.