Am 06.07.10 19:15, schrieb "Marcin W. Dąbrowski": > Hi. > > Today I hit something weird, when trying to see the history of one > of the files in my repository - `mtn log filename.ext` is showing > logs for other files than 'filename.ext'. > > I tried to find minimal case, and running the sequence you can see > presented below hits the "bug" - or to say this in other words — > it shows not exactly the information I'd like to see. > [snip] > I see two changelogs printed. I don't know why I see the changelog > for example.txt, nor why the order is chronological (normally it > should be reverse chronology - usually it is). > > So - is this by design (no, really?), or a bug?
I think this is a fall-out of the new restrictions code which landed in 0.48 (try out 0.47 and you see the expected behaviour). We now implicitely include all parents of a node in a restriction and as such, if you log "sec/second.txt", changes for "sec" and "" (the root node) are also logged. I'll try out a fix and switch the restriction handling mode to what we use also for 'revert', i.e. no implicit includes. Stay tuned and thanks for the report, Thomas. -- GPG-Key 0x160D1092 | tommyd3...@jabber.ccc.de | http://thomaskeller.biz Please note that according to the EU law on data retention, information on every electronic information exchange might be retained for a period of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
