Comments on: Mercurial: Initial Impressions http://www.jeffongames.com/2008/08/mercurial-initial-impressions/ This is Jeff. This is Jeff On Games. Tue, 31 Jan 2012 21:30:53 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: nofear http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-39953 nofear Thu, 22 Oct 2009 00:25:01 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-39953 Hi Jeff Could you post how did you setup the mercurial server with the ldap backend? I'm not able to find such information until now, so it would help me a lot. Thanks and keep it up :) Hi Jeff

Could you post how did you setup the mercurial server with the ldap backend? I’m not able to find such information until now, so it would help me a lot.
Thanks and keep it up :)

]]> By: Jeff http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-39029 Jeff Wed, 19 Aug 2009 13:07:10 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-39029 @Alen I didn't integrate with an AD server, but there are plenty of articles on using AD as an LDAP server out there. @Alen I didn’t integrate with an AD server, but there are plenty of articles on using AD as an LDAP server out there.

]]> By: Alen http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-39027 Alen Wed, 19 Aug 2009 09:20:14 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-39027 You say: The good: Mercurial was really easy to set up, even integrating LDAP into the push permissions system. I like it when things are that easy. Can you post how you configured apache/mercurial to authenticate with active directory? You say:
The good:
Mercurial was really easy to set up, even integrating LDAP into the push permissions system. I like it when things are that easy.

Can you post how you configured apache/mercurial to authenticate with active directory?

]]> By: dsp http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-33222 dsp Wed, 04 Mar 2009 01:05:03 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-33222 @ches bookmarks will be remote in the future. @ches bookmarks will be remote in the future.

]]> By: Ches http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-32064 Ches Tue, 20 Jan 2009 02:01:51 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-32064 Bookmarks are a nice step, but unfortunately they're hardly an analog to git branches at this point, because they're effectively local-only. It's still a useful extension, because I can get convenient named branch-like behavior locally while being able to delete them, but remote, temporary branches in git are very useful and remain the biggest utility that I think it has over hg. Bookmarks are a nice step, but unfortunately they’re hardly an analog to git branches at this point, because they’re effectively local-only. It’s still a useful extension, because I can get convenient named branch-like behavior locally while being able to delete them, but remote, temporary branches in git are very useful and remain the biggest utility that I think it has over hg.

]]> By: poko http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-31798 poko Fri, 09 Jan 2009 15:05:53 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-31798 just an FYI mercurial 1.1 introduced rebase (rebase ext) and git-like lightweight branches (bookmarks ext). just an FYI mercurial 1.1 introduced rebase (rebase ext) and git-like lightweight branches (bookmarks ext).

]]> By: abd http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-31779 abd Fri, 09 Jan 2009 00:33:13 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-31779 Try the SonicHg extension: http://kenai.com/projects/sonichg/pages/Home It has a pushlog hook that gathers the data. Try the SonicHg extension:

http://kenai.com/projects/sonichg/pages/Home

It has a pushlog hook that gathers the data.

]]> By: Jeff http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-30151 Jeff Fri, 14 Nov 2008 14:11:00 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-30151 A good suggestion for a quick fix without extensions, but not quite what I was looking for. A real solution would store the pushing user as metadata on the actual changes. Maybe have the name of the server, the date, and the user that did the push. That way we can see change 1-5 got pushed to the initial upstream by me, 6-7 got pushed by person X, then they all got pushed to the release server by person Y. Also, the other problem is that I'd want to make sure that the LDAP username is used over the mercurial username. A good suggestion for a quick fix without extensions, but not quite what I was looking for. A real solution would store the pushing user as metadata on the actual changes. Maybe have the name of the server, the date, and the user that did the push. That way we can see change 1-5 got pushed to the initial upstream by me, 6-7 got pushed by person X, then they all got pushed to the release server by person Y.

Also, the other problem is that I’d want to make sure that the LDAP username is used over the mercurial username.

]]> By: reto http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-30150 reto Fri, 14 Nov 2008 13:52:30 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-30150 To log the user who pushed a changeset I suggest you - create file /etc/mercurial/hgrc: [hooks] incoming = pushhook - create script /user/local/bin/pushhook: #!/bin/sh printf "\"%s\"\t\"%s\"\t\"%s\"\t\"%s\"\n" "$HG_NODE" "$USER" "$(date -u)" "$(hg log --template '{desc}' -r $HG_NODE | tr '\n' ' ')" >> .hg/pushlog as a result you whould have a pushlog in every project's .hg directory To log the user who pushed a changeset I suggest you

- create file /etc/mercurial/hgrc:

[hooks]
incoming = pushhook

- create script /user/local/bin/pushhook:

#!/bin/sh
printf “\”%s\”\t\”%s\”\t\”%s\”\t\”%s\”\n” “$HG_NODE” “$USER” “$(date
-u)” “$(hg log –template ‘{desc}’ -r $HG_NODE | tr ‘\n’ ‘ ‘)” >>
.hg/pushlog

as a result you whould have a pushlog in every project’s .hg directory

]]> By: Jeff On Games » Blog Archive » Mercurial Second Impressions http://www.jeffongames.com/2008/08/mercurial-initial-impressions/comment-page-1/#comment-26751 Jeff On Games » Blog Archive » Mercurial Second Impressions Thu, 21 Aug 2008 15:07:37 +0000 http://www.jeffongames.com/2008/08/mercurial-initial-impressions/#comment-26751 [...] use them to promote pre-push process. Right now, though, I quickly want to respond to a few of my initial impressions of [...] [...] use them to promote pre-push process. Right now, though, I quickly want to respond to a few of my initial impressions of [...]

]]>