Mercurial DVCS (mercurial) group
Notices
-
for i in ct-*x*/; do sed -i "s/\\/Work/\\/home\\/Processor\\/Work_TH5/" $i/da.rc; !hg -R $i ci -m "use linked work" $i/da.rc; done ← #bash!
-
Workflow Failures for Basic Usecases of #DVCS in !mercurial and !git → http://draketo.de/node/561 — “are you serious???” !fs
-
bzr revnos never did jump around when merging branches into a mainline; only if you steal mainline context, which is #bad-form in *any* DVCS
-
I generally set my shared #bzr branches to disallow `merge down, hijack mainline context, push up' behaviour: "append_revisions_only=True"
-
@rozzin what does mainline context mean?
-
-
!Freenet, !GNU (with the the !Hurd) and !Mercurial are in #GSoC 2013! → http://google-melange.com/gsoc/accepted_orgs/google/gsoc2013 *happy*
-
Arne Babenhauserheide likes this.
-
thanks!
-
-
@arnebab on the topic of mercurial, have you been keeping track of the version control discussion on emacs-devel?
- Arne Babenhauserheide repeated this.
-
@tekk I’m not on the list right now… are you? → you’re free to quote me for that.
-
@arnebab I lurk, but given the fact that I've never contributed to any gnu project(tried with gnu fm, copyright assignm…
Mike Linksvayer likes this. -
@tekk me neither: I’m a Hurd contributor, but no big GNU coder. I don’t think that matters when you show good arguments, though.
-
If you use !Mercurial exactly like !git, your workflow will be as elegant as !Python-code written by long-time #Java-Programmers
- Andreas Poisel and engelnyst repeated this.
-
@sud0er …line-long variable names (unneeded in Python due to namespaces), deeply nested packages (which require import from), …
-
@sud0er …getter and setter to keep people from accessing the precious internal variables (useless in a scriping language), etc.
-
@sud0er Essentially it means: Every system has its own optimal workflows. If you copy a workflow unchanged, it won’t be optimal.
-
@bkuhn Because of !GPLv3 !Mercurial moved *from* GPLv2 only *to* GPLv2 or later, so it could be used with GPLv3 licensed software
-
That's a good point. I'd forgotten that, which was dumb of me, b/c I helped !Mercurial do that! (they're a !Conservancy member).
Arne Babenhauserheide likes this. -
I remember it, because I complained about the “2 only” clause repeatedly - along with others :)
-
then seeing that actually work was great!
-
-
In the !hg record extension you can hit 'e' to edit the patch manually. Thanks to !emacs that provides convenient patch splitting.
-
!Mercurial 2.5 RC has been released ( !HG / !SCM ) http://mercurial.selenic.com/
about 4 months ago from web -
!Mercurial 2.4.2 has been released ( !HG / !SCM ) http://mercurial.selenic.com/
about 4 months ago from web -
!TortoiseHg 2.6.2 has been released ( !Mercurial / !HG / !SCM ) http://tortoisehg.org/
about 4 months ago from web -
!hg #PSA: Do not use the inotify extension, you may end up with non-ignorable files (they show up as both ignored and untracked)!
about 4 months ago from Choqok -
5-branch-types !git model to 2-branch !hg model with same functionality rev2: http://ur1.ca/ck4k5 ← much more readable
- Pamela Petterson repeated this.
-
transforming the 5-branch-types !git model to the 2-branch !hg model with the same functionality: http://draketo.de/node/513#fn:git-to-hg
- Arne Babenhauserheide likes this.
- Vasco Dias repeated this.
-
I heavily simplified my workflow for grafted micro-releases: http://draketo.de/node/513#graft-releases !hg #vcs #dvcs
-
How to do cherry-pick releases cleanly: http://draketo.de/node/513#fn:graft — a footnote for the !mercurial branching strategy
-
Test of the !hg #evolve extension for easier upstreaming → http://ur1.ca/chx68
-
#ILoveMercurial more and more whenever I hear !git users tell me that #DVCS has to be complicated… !hg is easy, fast and powerful
- Brent Reynolds and Rhianne Boyle repeated this.
-
@arnebab Tough shit. Mine's for my pleasure.
-
@jasonriedy that’s what you can make it, but (bites down smug comment) :)
-
@arnebab Takes more than one, at least for an optimal point.
-
!Mercurial 2.4.2 released: http://mercurial.selenic.com/wiki/WhatsNew — bugfixes and speedups
-
Does anyone know exactly how private Bitbucket's "private" !hg repositories are?
-
@jfm If you want something really private, upload your repo to !freenet and only pass the key to friends → http://ur1.ca/9iwfj !hg
-
Thanks, but unfortunately, it has to be reachable from a network belonging to The Man. Going to trade some security for convenience.
-
@jfm I also often have to do that, but occassionally I can do the Right Thing™… for repos which benefit from that, I use infocalypse
-
All Identi.ca content and data are available under the