monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] Incorporating debian/* changes in releases


From: Nathaniel Smith
Subject: Re: [Monotone-devel] Incorporating debian/* changes in releases
Date: Fri, 25 Aug 2006 14:34:17 -0700
User-agent: Mutt/1.5.12-2006-07-14

On Fri, Aug 25, 2006 at 03:21:27PM -0600, Shaun Jackman wrote:
> Hmmm, the problem seems to be that I omitted that second argument to
> mtn push. Could the pattern argument default to something more useful,
> like say the branch specified in _MTN/options? What is the current
> default patten? Should `mtn push' give a warning when nothing is
> pushed?

It defaults to whatever you pushed first (and tells you this when you
do that push).  Possibly it should state the pattern on later
pushes...

_MTN/options is not the right default, because the common case we want
to support is that you always push something like
"net.venge.monotone*", so you never have to worry if you've forgotten
to push some particular branch, etc.

You can see what the current default is by doing 'mtn ls vars'; look
for "default-exclude-pattern" and "default-include-pattern".

You can change the default by doing a push/pull/sync, and passing it
the --set-default flag.

-- Nathaniel

-- 
Damn the Solar System.  Bad light; planets too distant; pestered with
comets; feeble contrivance; could make a better one myself.
  -- Lord Jeffrey




reply via email to

[Prev in Thread] Current Thread [Next in Thread]