[PATCH 2 of 3] debugdag and debugindexdag: emit changelog/revlog DAGs as concise text

Matt Mackall mpm at selenic.com
Tue Feb 9 18:30:21 CST 2010


On Tue, 2010-02-09 at 08:25 +0100, Benoit Boissinot wrote:
> On Tue, Feb 09, 2010 at 08:05:21AM +0100, Peter Arrenbrecht wrote:
> > On Mon, Feb 8, 2010 at 11:21 PM, Benoit Boissinot <bboissin at gmail.com> wrote:
> > > On Mon, Feb 8, 2010 at 10:42 PM, Peter Arrenbrecht
> > > <peter.arrenbrecht at gmail.com> wrote:
> > >> # HG changeset patch
> > >> # User Peter Arrenbrecht <peter.arrenbrecht at gmail.com>
> > >> # Date 1265663003 -3600
> > >> debugdag and debugindexdag: emit changelog/revlog DAGs as concise text
> > >
> > > Can't you use the same command for both?
> > >
> > > debugindexdag without any argument could emit the changelog DAG.
> > 
> > Problem is that debugdag needs a repo, debugindexdag just a revlog.
> 
> some command are in optionalrepo, that could be the case for debugdag.
> 
> > I had first wanted to add a debugindex --dag option, but then realized
> > that there already is debugindexdot, so I copied that pattern.
> 
> Ok. And maybe debug*dag would be better in an extension. It doesn't
> *need* to be in core, and it isn't useful for daily work (except for hg
> devs).

Actually, I want this as a way to get info from users. They send me
their DAG dump, then I can recreate a repo using it and have a
topologically identical tree to look at, in a much more compact form
than graphlog or debugindex.

-- 
http://selenic.com : development and support for Mercurial and Linux




More information about the Mercurial-devel mailing list