[PATCH 0 of 4] Subrepository log

[Martin Geisler]

Matt Mackall <mpm at selenic.com> writes:

> Here's what it looks like:
>
> +Recursive log:
> +
> +  $ hg log -S -l 1
> +  changeset:   2:1326fa26d0c0
> +  tag:         tip
> +  user:        test
> +  date:        Thu Jan 01 00:00:00 1970 +0000
> +  summary:     2-3-2
> +  
> +  log in subrepository foo
> +  changeset:   3:65903cebad86
> +  tag:         tip
> +  user:        test
> +  date:        Thu Jan 01 00:00:00 1970 +0000
> +  summary:     2-3-2
>
> Yeah, that marker is not terribly useful. But I think there are bigger
> issues here.

We're just thinking out loud here... but Erik had a new idea: we could
include a 'subrepository:' line in the output so that it looks like
this:

  $ hg log -S -l 1
  changeset:     2:1326fa26d0c0
  tag:           tip
  user:          test
  date:          Thu Jan 01 00:00:00 1970 +0000
  summary:       2-3-2

  subrepository: foo
  changeset:     3:65903cebad86
  tag:           tip
  user:          test
  date:          Thu Jan 01 00:00:00 1970 +0000
  summary:       2-3-2

  changeset:     2:12303cebad86
  user:          test
  date:          Thu Jan 01 00:00:00 1970 +0000
  summary:       1-1-1

Imagine that the 'subrepository:' line is highligted in red/orange so
that it stands out against all the yellow 'changeset:' lines.

The normal changeset displayer logic will hide the line for consequtive
changesets within the same subrepository.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://aragost.com/mercurial/