Rollback ate my commit message! (issue 1635)
Mark Williamson
maw48 at cantab.net
Wed Nov 18 13:16:09 CST 2009
On Wednesday 18 November 2009 18:30:28 Greg Ward wrote:
<snipped some stuff>
> So I am proposing to fix it in a way that benefits all Mercurial users
> all of the time. Cost: 3 lines of code and a little extra I/O for
> each commit. If you really don't think it's worth it, then I'll just
> do it early in our pretxncommit hook. It will stop annoying me, and
> will continue to annoy the invisible people who don't complain.
> (Possibly an empty set, but I doubt it.)
Not an empty set, since it contains me. I've always regarded my losing a
commit message because of using rollback as being my own fault but I'd welcome
a mechanism that provided a cheap and simple means of saving me from myself.
If I had to define hooks or install an extension to do this then I'd probably
never get round to it. But if there was a quick-n-dirty helper that didn't
introduce performance or maintenance concerns it would repeatedly save me
minor instances of frustration.
Cheers,
Mark
>
> As for "a) your commit edit helper", do you mean a mythical shell
> script run by hg that in turn runs my $EDITOR? But I don't have one,
> and don't want to need one. I've never needed one with CVS or
> Subversion, so why should I need one for Mercurial? Oh yeah...
> because rollback ate my commit message, and that doesn't happen with
> CVS or Subversion -- even when a server-side commit hook rejects my
> commit.
>
> Greg
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>
More information about the Mercurial-devel
mailing list