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. #v+ mtn -d mtn.mtn db init mtn -d mtn.mtn setup . -b mtn.bug.log echo x> example.txt mtn add example.txt mtn ci -m "Added new file." mkdir sec cd sec mtn -d ../mtn.mtn setup . -b mtn.bug.sec echo y> second.txt mtn add second.txt mtn ci -m "Added new file, second branch." -b mtn.bug.sec cd .. mtn up -r h: -b mtn.bug.log rm -rf sec mtn merge_into_dir --update -m "merge_into_dir src" mtn.bug.sec mtn.bug.log sec cd sec mtn log --no-merges second.txt #v- 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? PS: mtn version --full gives monotone 0.48 (base revision: 844268c137aaa783aa800a9c16ae61edda80ecea) Running on : Windows NT/2000/XP/2003 (5.1, build 2600, Service Pack 3) on ia32 (level 6, rev 3846) Sincerely, -- Marcin W. Dabrowski _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
