Vladimir Marek wrote:
> That's true. But you don't need to recommit all the time. Just before
> final putback should be fine. If you commit often in your workspace, it
You missed my point - I need to recommit after each code review
iteration for webrev refreshment since generally code reviewer
>+-+ pull +-+ pull +--+
>| onnv-clone |-->| workstation |->| bld. machine |
>| | | repo| | repo |
>+-+ +-+ +--+
>
> This means doing 'hg commit' inste
James Carlson wrote:
> Why not go to the build workspace and just pull from the desktop
> workspace? Pulls are pretty fast, even over large distances (quite a
> change from Teamware, even with nifty things like turbo_flp).
Like this ?
+-+ pull +-+ pull +---
Vladimir Kotal writes:
> Vladimir Marek wrote:
>
>
>
> > That's true. But you don't need to recommit all the time. Just before
> > final putback should be fine. If you commit often in your workspace, it
>
> You missed my point - I need to recommit after each code review
> iteration for webrev
Vladimir Kotal writes:
> Like this ?
>
>+-+ pull +-+ pull +--+
>| onnv-clone |-->| workstation |->| bld. machine |
>| | | repo| | repo |
>+-+ +-+ +--+
[ ... ]
> Because it fits the Teamware model I've been using and which was so
> convenient and fast [**] : 'wx backup -t' on my workstation, followed by
> 'wx restore -f && nohup nightly incremental.sh &' on the build machine
> did the trick just fine. Moreover, multiple invocations of the same
Richard Lowe wrote:
> I'd imagine, given the above, that you're using backup/restore to move
> changes between machines? If so, why would you do that rather than
Exactly. My workstation sits under my desk in Europe and has only 2 CPUs
so nightly takes forever to complete (besides, the machine
Vladimir Kotal wrote:
> Hi all,
>
> lib/python/onbld/Scm/Backup.py does backup of .hg/hgrc which contains
> the path to parent. This breaks things if backup repository uses local
> clone and restore repository another local clone (model where sparse
> builds are done locally and nightlies on bu
Vladimir Kotal writes:
> Exactly. My workstation sits under my desk in Europe and has only 2 CPUs
> so nightly takes forever to complete (besides, the machine is needed for
> other tasks). It uses local clone mirror (served over NFS over LAN) to
> speed up initial 'hg clone' [*]. After I am done
Vladimir Kotal writes:
> Vladimir Kotal wrote:
>> Hi all,
>>
>> lib/python/onbld/Scm/Backup.py does backup of .hg/hgrc which contains
>> the path to parent. This breaks things if backup repository uses local
>> clone and restore repository another local clone (model where sparse
>> builds are
Hi all,
lib/python/onbld/Scm/Backup.py does backup of .hg/hgrc which contains
the path to parent. This breaks things if backup repository uses local
clone and restore repository another local clone (model where sparse
builds are done locally and nightlies on build machine e.g. in another
geo
11 matches
Mail list logo
