Re: Uhmmm, can't commit????

Olivier Andrieu writes:

 >  monotone --message="update of monotone.pot" commit

I was baffled by this at first too, but then I added

  alias mcommit='monotone commit --message'

to my .bashrc and all was well.

By they way: The changes from the restriction branch are
great! I had devised about a dozen scripts that wrapped
monotone to do what it does out-of-the-box now, and none of
those scripts ever worked reliably. ;-) So thanks for adding
these features.

I noticed one change that I'd like to see reversed though:
When you are inside a checked-out repository and want to
check out a different branch as a subdirectory, then you
could just write

  monotone --branch=other co foo

and Monotone would automatically find the --db argument from
the current MT/options file. The new version doesn't do that
anymore, though, it requires the database to be specified
again. This is unfortunate in the case where you'd like to
check out subdirectories via Makefile, for example. I often
have a target like this in my build system:

  init-src::
          @rm -f MT/monotonerc
          @ln -s ../.monotonerc MT/monotonerc
          monotone --branch=to.cryp.hs.dns co dns
          monotone --branch=to.cryp.hs.email co email
          monotone --branch=to.cryp.hs.blockio co blockio
          monotone --branch=to.cryp.hs.child co child
          monotone --branch=to.cryp.hs.syslog co syslog
          monotone --branch=to.cryp.hs.hopenssl co hopenssl

With the new version, I either have to hard-code the path to
the database into the Makefile, or I have to parse it out of
MT/options myself.

A way to remedy that safely would be to add something along
these lines:

  monotone cat default db       -- prints current db path
  monotone cat default branch   -- prints current branch

Then I could use monotone to extract the information in
MT/options.

Any thoughts about that?

Peter