Re: [Monotone-devel] automate sync display branches?

[Stephen Leake]

Timothy Brownawell <address@hidden> writes:

> On 09/13/2010 05:48 AM, Stephen Leake wrote:
>> Stephen Leake<address@hidden>  writes:
>>
>>> Thomas Keller<address@hidden>  writes:
>>>
>>>> As I've written earlier on IRC it
>>>> might be a good idea to team up with Tim (nvm.netsync) - see the
>>>> discussion here:
>>>>
>>>> http://colabti.de/irclogger/irclogger_log/monotone?date=2010-09-11#l55
>>>
>>> That does look useful. Tim; should I work directly in nvm.netsync, or
>>> branch from there (nvm.netsync.automate)?
>
> Sorry, I've been a bit occupied with other stuff most of the weekend.
>
>> First attempt pushed in nvm.netsync.automate; the data collection is
>> there, the output and tests need work. The dryrun and automate
>> stuff do not actually integrate well.
>
> I've got some changes in nvm.netsync that should make it work better.
> All the counts/items for dry-run output and the notification hooks are
> stored in future_set objects, which currently live in
> netsync_connection_info. So it should be possible to just use these,
> and probably the automate printer doesn't have to care about dry-run
> vs not.

Yes, that is cleaner. I just didn't have the courage to make that many
changes.

> Right now there's a really nasty hack for creating a
> netsync_connection_info from nothing in case the session didn't get
> one when created (server accepting a connection), so probably the
> future_set objects need to live somewhere new (that still gets passed
> into the session, so the caller can get the id's / counts back).

I'll see if I can figure that out. 

-- 
-- Stephe