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

[Stephen Leake]

Thomas Keller <address@hidden> writes:

> Am 12.09.10 21:17, schrieb Stephen Leake:
>> 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)?
>> 
>> I think it makes sense to not call the note_netsync_* Lua hooks from the
>> automate version, since the intent is that the front-end will process
>> the automate output, not the hooks. That way save some processing time,
>> and we don't have to worry whether the hooks will screw up the automate
>> output.
>
> I'm not sure about that - out of the box these hooks do nothing bad
> since they do not print out anything and if we follow your reasoning we
> might start disabling other hooks which might interfer with the output
> somehow. In the end its the user's problem to take care the hooks do not
> interfer with automate's output and we already gave a set of tools into
> the hands of the user / automate implementor
>
> 1) in guitone for example I start every mtn instance with
> --no-builtin-rc (previously --norc) to avoid side effects

Or I could override just the netsync hooks, leaving others intact.

> unless
> there isn't a very (very) good reason to restrict some functionality,
> then I think we shouldn't do it.

ok, it was just a thought. 

-- 
-- Stephe