© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
On our 2a format repo:
jal@odeon:
-------
revno: 236 [merge]
committer: Wouter
branch nick: vp-trunk
timestamp: Fri 2009-11-13 15:03:23 +0100
message:
Proficon integratie.
-------
revno: 4
committer: Frits Jalvingh <email address hidden>
branch nick: vp-trunk
timestamp: Thu 2009-08-27 20:30:46 +0200
message:
Initial commit of vp-trunk
-------
revno: 2
committer: Frits Jalvingh <email address hidden>
branch nick: vp-3.2-hot
timestamp: Thu 2009-08-27 20:20:17 +0200
message:
Initial commit of vp-3.2-hot
-------
revno: 1
committer: Frits Jalvingh <email address hidden>
branch nick: vp-3.1-hot
timestamp: Thu 2009-08-27 20:16:59 +0200
message:
Initial commit of 3.1-hot
-------
Use --include-merges or -n0 to see merged revisions.
Then try:
jal@odeon:
-------
revno: 236 [merge]
committer: Wouter van Vliet <email address hidden>
branch nick: vp-trunk
timestamp: Fri 2009-11-13 15:03:23 +0100
message:
Proficon integratie.
modified:
viewpoint/
---
revno: 130.113.20
committer: Wouter van Vliet <email address hidden>
branch nick: vp-3.3-hot
timestamp: Fri 2009-11-13 14:56:13 +0100
message:
Refactor & toevoegen commentaar.
modified:
viewpoint
This is inconsistent: log lies about what changed in some contexts. What is worse, it looks like that commit 236 somehow touched almost *all* files in the repo: asking the log for lots of files show those as changed in that commit too.
This looks a bit like the effect we had when we hit bug 415508; but the repository was recreated from scratch since then and nothing from the failed repository was used in the new one. And regardless of the reason *why* this occured- if this commit has a lot of changed texts attached to it it should show them, so the error becomes obvious quicker also.