marcinkuzminski

11 ms·

61.
Look before you paste from a website to terminal(lifepluslinux.blogspot.com)
140 points by marcinkuzminski 10y ago|41 comments
62.
by marcinkuzminski 10y ago
There are companies adopting mercurial as they VCS of choice, either by moving out of svn, or choosing a new VCS
63.
by marcinkuzminski 10y ago
can you share how many machines handles gitlab.com currently?
64.
by marcinkuzminski 10y ago
Speaking as someone that works with Mercurial on daily basis, and also makes/sells software that supports Mercurial. I can tell you it's far from beeing legacy.
65.
by marcinkuzminski 10y ago
It's now based on pyramid 1.6
66.
by marcinkuzminski 10y ago
we need to make the web ones get the same experience level then. It's great to have it all there. Were you leave your inline notes, there's a live communication part, all feedback from automated code checkers etc.
67.
by marcinkuzminski 10y ago
it becomes more important when you use this for code-review. Then reach diffs makes more sense. Once you start using them you don't want to go back :)
68.
by marcinkuzminski 10y ago
Bitbucket server is written in Java while Bitbucket.com in Python. Those are two different products. That's why the Enterprise version supports only GIT. Check our RhodeCode for Enterprise SCM tool that supports Mercurial too.
69.
by marcinkuzminski 10y ago
Interesting, from our point of view at RhodeCode, allowing modification of code often benefited our support team. When testing some real edge cases, we were able to inject additional debug code to pinpoint the problems. It actually helps IM
70.
by marcinkuzminski 10y ago
based on the how Github Enterprise works, they probably use the same technology, meaning ElasticSearch. I wonder how often they rebuild the indexes, and scan for new commits. That's an interesting problem to solve actually
71.
by marcinkuzminski 10y ago
Inspired by Mercurial, we built such functionality for GIT backend in RhodeCode. So the numeric identifiers are used now for all 3 backends we support. Kallithea has it also implemented for GIT. I personally never like the meaningless hashe
72.
Using auth tokens as an alternative to SSH keys in VCS usage(rhodecode.com)
3 points by marcinkuzminski 10y ago|0 comments
73.
by marcinkuzminski 10y ago
For the source code management, you can try rhodecode. There's a community version too.
74.
by marcinkuzminski 10y ago
As for Mercurial, I'd this RhodeCode is the company going for it, since we heavily invest in supporting Mercurial in our product.
75.
by marcinkuzminski 10y ago
+ there are nice tools like RhodeCode to work with Mercurial repositories.
76.
by marcinkuzminski 10y ago
IMHO it's odd approach to the problem. I'd rather ask the author (who knows best in this case) to split this into two separate parts that can be nicely merged.
77.
Mercurial 4.0 has been released(mercurial-scm.org)
6 points by marcinkuzminski 10y ago|0 comments
78.
by marcinkuzminski 10y ago
Just read this: http://stevelosh.com/blog/2013/04/git-koans/ And then think about that Mercurial simply makes handling branches/updates/resets in a very clean and consistent way.
79.
by marcinkuzminski 10y ago
Exactly, there is the flexibility. IF you need to track source of commits together with the permanent branch info you use Mercurial branches, if you want a "symlink branches" in GIT style, bookmarks are the way to go. It works nic
80.
by marcinkuzminski 10y ago
I think GIT staging area wouldn't make it so nice to use in the end. Unless the whole thing is abstracted more, but then we get into the gitless discussion again.
81.
by marcinkuzminski 10y ago
> I.e. having a basic understanding of how git manages its data makes hardly leaves me with situations and repository states that I cannot resolve. If your dvcs allows you to get to that odd situation then it's already bad. Think ab
82.
by marcinkuzminski 10y ago
The latests iteration of hg crecord which is an interactive selection tool for chunks (see it in action here: http://g.recordit.co/BfbSa7cMXn.gif ) Is far far better than git staging area. Intuitive to use, i can submit hour
83.
by marcinkuzminski 10y ago
I think what Mercurial brings here is that even if you have a repo and you do a force-push you keep all the heads. Thus it's almost like a history of changes. I think if you do a code-review and you get the final state of the repo to c
84.
by marcinkuzminski 10y ago
Here's a blog post on how to use Bookmarks in Mercurial workflow using code-review. We back ported from one of the guys that works for us and described our workflow: https://rhodecode.com/blog/120/mercurial-wo
85.
by marcinkuzminski 10y ago
That is not normal. We at RhodeCode works with some of biggest Mercurial behind-the-firewall setups. We have one customer which uses a global VPN for their few instances. They always measure Mercurial pull performance using a load tests. Fo
86.
by marcinkuzminski 10y ago
Thanks for sharing, actually those two first ones was our main focus from beginning. We worked back in the days with Unity which was using kiln to make the code-review workflows similar. If you miss kiln, you should check RhodeCode out, and
87.
by marcinkuzminski 10y ago
What's you best KILN feature ? I wonder if we can adopt it at RhodeCode
88.
by marcinkuzminski 10y ago
CTO of RhodeCode here. If you use phases (draft/secret/public) correctly it's really close to being mutable. For example all our devs forks are having non-publishing repositories since it's a private non-shared space. By
89.
by marcinkuzminski 10y ago
Hopefully ! We spend a lot of time on our own to scale our Mercurial backend. Currently with the http based vcs-server and gevent we can support a lot of concurrent hg operations, but imho that thing can put it on the next level... I wonder
90.
by marcinkuzminski 10y ago
CTO of RhodeCode here. This is exciting, we need to take a look from our side how this would affect our product. I really like that Mercurial is gaining some traction with the big guys, which tries to solve some nice problems at scale.

More ›