5 ms·
You're not the only one, I too like it. But there comes a time when you want your merges and rebases to work predictably (absolutely never reshuffling your line
by pmeunier 5y ago
You're not the only one, I too like it. But there comes a time when you want your merges and rebases to work predictably (absolutely never reshuffling your lines randomly), your conflicts to be solved once and for all (without hacks like rerere!).
Maybe you may also want your tool to serve your workflows and not the opposite.
- arbaal 5y ago> Maybe you may also want your tool to serve your workflows and not the opposite. This sounds like you claim that pijul serves all workflows well, which would contradict my own experience. I'm so used to think in branches / PRs (to display a history and showing lineages), that I find the current way of handling channels/patches of pijul alien. Right now I would need to break my workflow in my daily operation to use pijul.
- pmeunier 5y agoYou can use branches in Pijul if you want, but you can't use patch commutation in Git.
- speed_spread 5y agoThat was a shot at git, not a claim that pijul supports all workflows. Anyway, breaking the workflow when switching tools is generally expected. It's a moment to review your assertions.