repository - Mercurial unreliable sub-repos. Any alternative? -
I'm trying to be masculine, but I'm crazy about it.
I am converting it from SVN to thinking that, in addition to the promise of better workflow, I use GIT in contract work, so I get full distributed ideas. I choose the finesse for the promise of more simplicity and support of better windows.
I am a single developer, I am working in a project that is 5 different repos
Generally, I commit every single repo, then it is rooted I am pushing with Root / Root.
But I found that:
-
2 There is a way to disable it for 2 consecutive things?
-
There is no GUI that actually works for my workflow (I use McHG, Tortoise HG and try other half endeavors). For practical push / pull behavior, I have to come back to the order line. No GUI understands subreparo, it does not seem that there is a problem of 2-head, so I need to merge / merge into the command line.
-
But the worst thing is that subrepos are very unreliable. In about 2-3 days I get "aborted: unknown amendment ****". Sometimes "+" happens at the end of hex value, not others.
Sometimes the only change is in the repo.
I do not want to cure this behavior, I am working for the above.
- Prepare each sub report
- Finally, push + Bring, whatever comes to understand ... and if working with the available GUIS is better.
You are a little confused in my humble opinion. Versoine control is distributed to the mercurial and GIT, so the repository always happens ... same.
You have your copy of the repository with all the history, there is no "everyone" -trace.
All repositories are "peers", and you can use them to develop "all" clones.
Take a look at this nice tutorial
Hope it helps
Comments
Post a Comment