Issue 100: In some condition, there is no log info for almost new changeset after pretxncommit http://bitbucket.org/tortoisehg/stable/issue/100/in-some-condition-there-is-no-log-info-for-almost-new-changeset-after
DannyWan on Thu, 2 Apr 2009 08:06:04 +0200: Comment: Hi Steve, Unfortunatly, I have to reopen this bug. It seems sometimes it works and sometimes it won't. We try to narrow down the conditions that may fail the log to work. It seems that it works fine when you test this in a repository you just created, but if you test it in a repository that you have cloned, it may fail. When we try to display the revision number, this one is empty, which may cause in fact that the log can not be printed. Of course the rest of the conditions are still valid, that means, you should try this when commiting from the **root** of a **cloned** repository. We tested this with your own pretxncommit example. Changes: status: resolved -> open version: 0.7.1 -> 0.7.3 -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue. ------------------------------------------------------------------------------ _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
