Fwd: im.pidgin.pidgin: edd672a79a29dc97a942d9520e7a3b93519af9d4

[Jeff Connelly]

On Jan 27, 2008 11:16 AM, John Bailey <rekkanoryo at rekkanoryo.org> wrote:
> Jeff Connelly wrote:
> > My Cygwin installation, for some reason, prevents mtn from reading
> > commit messages from /tmp that were written in $EDITOR. So I have been
> > saving the commit message to a file and passing a flag to mtn to
> > specify the message, but I used -m instead of --message-file. Will try
> > to be more careful in the future. What would be the best thing to do
> > about these existing useless commit messages?
> Are you using the native win32 mtn binary, or did you install the cygwin
> package?  If you're using the native win32 binary, this is the problem--it
> doesn't understand cygwin's UNIX-style paths and instead requires Windows-style
> paths.
Cygwin package; I have my TMP and TEMP envars set to /tmp, but mtn
commit opens vim editing C:\tmp\mtn.XXX which mtn can't find. Ah, I
found out the problem - I needed to install vim from Cygwin, instead
of the native Win32 vim. Now it works :).

> You can add additional changelog certs to revisions by using 'mtn cert REVISION
> changelog', hitting enter/return/newline, typing your new changelog entry, and
> pressing control-D when done.  This behavior may be slightly different in
> Windows.
Cool, this works well. I just did this for my revisions with a log
message of 'a'. The new changelog entry is shown above the useless
one, so this looks like a good solution. Hope that the new log
messages are helpful.

Regards,
-Jeff

P.S.: Apologies if you receive this message twice.