4 ms·
That could work. If your local patches are complex enough you could even rearrange them using patch commutation. At the moment, Pijul is in a state where there
by pmeunier 5y ago
That could work. If your local patches are complex enough you could even rearrange them using patch commutation.
At the moment, Pijul is in a state where there is just one remaining feature I want to implement before beta, with a massive expected impact on disk space (and a limited impact on speed as well).
For the kind of "smaller (but essential) features" like what you're suggestion, there are tons of those, and we can totally implement them after beta. Git export is a common request we get, though. I'm just scared of how people will react when they export and then reimport their patches elsewhere, and get tons of fake conflicts.
- kadoban 5y agoI think you will get a lot of complaints, which is unfortunate, but many many will understand that it's not going to be perfect. I was there for the period of switching from svn to git, and similar things happened. Really the only way I even learned git itself is because I could use git locally and the rest of my team couldn't tell. Regardless though, pijul is really cool. I just badly want to be able to use it at my day job :)
- renox 5y agoAnd yet given that git is the current "default" VCS, it's very important that this is/will be "as smooth as possible".. I wonder if it wouldn't be possible to memorize "git order" of patches when importing them in Pijul to be able to re-export them in the same order as they were imported before.