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

[Shaun Jackman]

On 8/23/06, Nathaniel Smith <address@hidden> wrote:
> I don't have those revisions.  Are you sure you pushed them to
> venge.net?

I thought I had...

$ mtn push venge.net
mtn: connecting to venge.net
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:       21,045 |   34 |     6,975
mtn:  bytes in | bytes out | certs out | revs out
mtn:     2.6 k |     3.0 k |       0/0 |      0/0
mtn: successful exchange with venge.net
$ mtn push venge.net net.venge.monotone
mtn: connecting to venge.net
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:       14,098 |   27 |     4,665
mtn:  bytes in | bytes out | certs out | revs out
mtn:   649.4 k |   589.7 k |       8/8 |      2/2
mtn: successful exchange with venge.net

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?

Cheers,
Shaun