diff tests/test-subrepo-deep-nested-change.out @ 11112:4a9bee613737

subrepo: print paths relative to upper repo root for push/pull/commit This makes more sense when using multiple levels of nesting. This happens to help a lot in a case where 3 projects of mine all use the same makefile helper project as a sub. A fourth project use these first three projects and current output made it very hard to figure which makefile helper was committed. it looked more like the project was committed/pushed/pulled three times in a row than dealing on three different repos.
author Edouard Gomez <ed.gomez@free.fr>
date Sat, 01 May 2010 23:05:22 +0200
parents 22f5ad0b5857
children
line wrap: on
line diff
--- a/tests/test-subrepo-deep-nested-change.out	Sat May 01 23:05:22 2010 +0200
+++ b/tests/test-subrepo-deep-nested-change.out	Sat May 01 23:05:22 2010 +0200
@@ -50,7 +50,7 @@
  revision c57a0840e3badd667ef3c3ef65471609acb2ba3c
 % Modifying deeply nested sub2
 committing subrepository sub1
-committing subrepository sub2
+committing subrepository sub1/sub2
 % Checking modified node ids
 cloned ffe6649062fe tip
 cloned/sub1 2ecb03bf44a9 tip