Package: mercurial Version: 0.9.5-3 Severity: minor
When mercurial runs meld to do a merge, it needs to say which window is which. This is doubtless obvious to Mercurial's developers and other experienced users, but, let me tell you, it's a doozy of a question the first time you use it. There is no obvious documentation on either the mercurial or meld web sites. Adding documentation would help, but a better design would be to make it more obvious to the user. One way to help would be to make the three file names more obviously meaningful. Perhaps one could be /tmp/hg-merge-input-20:134124-21312.tmp where the 20:124124 specifies node 20:whatever. Perhaps the third could be /tmp/hg-merge-result-23:12131-123123.tmp again, making its role more obvious and also giving a node number. (Sorry for the terminology. It's probably not "nodes", but you node what I mean. :) ) Alternatively (or additionally) hgmerge could print out a one-line hint when it starts up one of the GUI merge tools. Something like "Merge FILENAME into the rightmost window". -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages mercurial depends on: ii libc6 2.7-6 GNU C Library: Shared libraries ii python 2.4.4-6 An interactive high-level object-o ii python-support 0.7.6 automated rebuilding support for p Versions of packages mercurial recommends: ii meld 1.1.5.1-2 graphical tool to diff and merge f ii rcs 5.7-21 The GNU Revision Control System -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
