Comments for x.zpuppet.org http://x.zpuppet.org blog Fri, 27 Nov 2009 15:39:04 -0600 http://wordpress.org/?v=abc hourly 1 Comment on mercurial tasks extension by Dilip http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-77 Dilip Fri, 27 Nov 2009 15:39:04 +0000 http://x.zpuppet.org/?p=56#comment-77 Just explored mq! the same stuff can be done using it.if we think each task as a patch! :) Just explored mq! the same stuff can be done using it.if we think each task as a patch! :)

]]> Comment on mercurial tasks extension by Dilip http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-76 Dilip Tue, 03 Nov 2009 08:40:47 +0000 http://x.zpuppet.org/?p=56#comment-76 A great extension. But won;t work on windows D:\repos\hgoff>hg task *** failed to import extension tasks from "D:\repos\hgoff\.hg\tasks.py": [Errno 22] Invali d argument hg: unknown command 'task' Mercurial Distributed SCM A great extension. But won;t work on windows

D:\repos\hgoff>hg task
*** failed to import extension tasks from “D:\repos\hgoff\.hg\tasks.py”: [Errno 22] Invali
d argument
hg: unknown command ‘task’
Mercurial Distributed SCM

]]> Comment on mercurial tasks extension by Dilip http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-75 Dilip Fri, 23 Oct 2009 09:06:17 +0000 http://x.zpuppet.org/?p=56#comment-75 Great! This will prevent me pushing all incomplete tasks! Great! This will prevent me pushing all incomplete tasks!

]]> Comment on mercurial tasks extension by Sander Smits http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-68 Sander Smits Mon, 11 May 2009 13:21:22 +0000 http://x.zpuppet.org/?p=56#comment-68 This is exactly what kept me from switching from Git to Mercurial! Git's cheap local branches are the killer feature for me and your tasks extension seems to provide the same functionality. Great! I sure hope this ends up in the core. This is exactly what kept me from switching from Git to Mercurial! Git’s cheap local branches are the killer feature for me and your tasks extension seems to provide the same functionality. Great! I sure hope this ends up in the core.

]]> Comment on mercurial tasks extension by Aaron http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-66 Aaron Fri, 01 May 2009 18:20:19 +0000 http://x.zpuppet.org/?p=56#comment-66 Thanks for the writeup! I had read your previous post about bookmarks and found it handy. I like bookmarks, but what I wanted was more like git branches, which is what the tasks seem to do. This matches my personal workflow almost exactly. Thanks again! Thanks for the writeup! I had read your previous post about bookmarks and found it handy. I like bookmarks, but what I wanted was more like git branches, which is what the tasks seem to do. This matches my personal workflow almost exactly. Thanks again!

]]> Comment on mercurial tasks extension by João Marcus http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-65 João Marcus Thu, 30 Apr 2009 13:50:24 +0000 http://x.zpuppet.org/?p=56#comment-65 I use hg mainly to have a personal VCS on top of a main CVS repo. I use the one branch per feature/bugfix approach, and this is exactly what I was looking for. Bookmarks were close, but this extension was a perfect match for my needs. Thanks a lot! I use hg mainly to have a personal VCS on top of a main CVS repo. I use the one branch per feature/bugfix approach, and this is exactly what I was looking for.
Bookmarks were close, but this extension was a perfect match for my needs. Thanks a lot!

]]> Comment on mercurial tasks extension by Excelsior » Mercurial tasks http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-64 Excelsior » Mercurial tasks Tue, 21 Apr 2009 07:10:07 +0000 http://x.zpuppet.org/?p=56#comment-64 [...] mercurial tasks extension [...] [...] mercurial tasks extension [...]

]]> Comment on mercurial tasks extension by alu http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-63 alu Fri, 10 Apr 2009 22:26:57 +0000 http://x.zpuppet.org/?p=56#comment-63 Hi Merwok, By "core Mercurial" you mean without use of an extension? I don't think will happen anytime soon. I think there is an effort to merge the functionality of shelve, attic, mq and pbranch, into one extension (http://www.selenic.com/pipermail/mercurial/2009-February/024170.html). I think bookmarks/tasks are a bit different, even though tasks shares minimal overlap with attic with the "auto.stash" feature. -Alex Hi Merwok,
By “core Mercurial” you mean without use of an extension? I don’t think will happen anytime soon.
I think there is an effort to merge the functionality of shelve, attic, mq and pbranch, into one extension (http://www.selenic.com/pipermail/mercurial/2009-February/024170.html).
I think bookmarks/tasks are a bit different, even though tasks shares minimal overlap with attic with the “auto.stash” feature.
-Alex

]]> Comment on mercurial tasks extension by Merwok http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-62 Merwok Fri, 10 Apr 2009 20:05:52 +0000 http://x.zpuppet.org/?p=56#comment-62 One gets quickly lost amidst named branches, bookmarks, pbranches, topic branches and tasks. However, the workflow you describe seems handy and intuitive. Are there any plans to get one official way to have this functionality in core Mercurial? Cheers, Merwok One gets quickly lost amidst named branches, bookmarks, pbranches, topic branches and tasks. However, the workflow you describe seems handy and intuitive. Are there any plans to get one official way to have this functionality in core Mercurial?

Cheers, Merwok

]]> Comment on mercurial tasks extension by alu http://x.zpuppet.org/2009/03/09/mercurial-tasks-extension/comment-page-1/#comment-61 alu Fri, 10 Apr 2009 20:02:31 +0000 http://x.zpuppet.org/?p=56#comment-61 Hi Bradford, Yes, the plan is to eventually have task information pushable/pullable. I know that there are some plans to have bookmarks sent over the wire and I was counting on using the same mechanism. I have some ideas about having tasks information live in their own separate repo inside .hg/tasks. There might be some complicated merging that needs to be done when two people work on the same task. I never thought about sharing stashes though. The centralized repo for tasks and task stashes that you suggest, would that simply be for allowing others to view incompleted task work (and backup)? And not necessarily allow two people to work on the same task? I will look at how the attic extension uses a centralized repo for attic changes. Thanks, Alex Hi Bradford,
Yes, the plan is to eventually have task information pushable/pullable. I know that there are some plans to have bookmarks sent over the wire and I was counting on using the same mechanism.

I have some ideas about having tasks information live in their own separate repo inside .hg/tasks. There might be some complicated merging that needs to be done when two people work on the same task. I never thought about sharing stashes though.

The centralized repo for tasks and task stashes that you suggest, would that simply be for allowing others to view incompleted task work (and backup)? And not necessarily allow two people to work on the same task?

I will look at how the attic extension uses a centralized repo for attic changes.

Thanks,
Alex

]]>