Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is incorrect...However I would probably not use hg rebase on Mercurial queues, which are meant to be managed by mq extension commands.

You completely contradicted your own claim already.

This is exactly what I'm complaining about: Mercurial Queues are diff and patch. And you need Mercurial Queues for decent Mercurial workflows.

I think most of the git vs. mercurial debates are non-productive because proponents of one tool don't know the other tool well enough to argue against it.

I use Mercurial extensively and on a daily basis, so I think I'm qualified to talk about it. People who claim the complaint is invalid should do Mercurial users a favor and point out a workflow that avoids the issue. I'm still waiting (and manually merging all my patch queues whenever I get a conflict in a topmost patch).



I did not explain myself correctly. What I meant is I would not even use queues at all. I would instead use the plain old hg commit and hg rebase.

Try this workflow.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: