hg as a bugzilla?

Michael Diamond dimo414 at gmail.com
Fri Dec 23 11:46:51 UTC 2011


On Fri, Dec 16, 2011 at 4:42 AM, Michael Diamond <dimo414 at gmail.com> wrote:

> To summarize my discussion with Ryan, he wants to be able to launch the
> details editor from a script without needing to know the issue prefix.  A
> prefix is output by `hg b add`, but it's not machine-parseable without some
> string manipulation.  My first suggestion was a simple shell script,
> something like:
>
> #!/bin/bash
> prefix = `hg b add $*`
> hg b edit ${prefix:10:10}
>
> Not the most robust solution, but it should work.  The better alternative,
> which I will try to implement soonish, would be a -e flag for the add
> command, which launches the editor for the newly created issue.
>
> I'm pleased to report that the -e flag functionality is now available for
testing on the development b repository:
http://hg.digitalgemstones.com/hg/b-dev/

I'd very much appreciate if anyone interested in this functionality could
pull down the dev repository and give it a spin.  It's logged as issue #87.

In addition, I think it would be nice to add a config (or CLI) parameter to
> create the default empty details file automatically when the issue is
> logged.  As noted in the readme, b functions correctly regardless of if a
> details file exists, but I think some larger use cases would want the file
> to always exist, and have it be tracked right away when the issue is
> created.
>

After implementing this feature (issue #83) and updating the readme, I'll
release all these improvements as 0.6.1 on the stable repository sometime
after the new year.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20111223/5207de99/attachment-0002.html>


More information about the Mercurial mailing list