[scm-migration-dev] hg backup/restore loses parent

by your changes. You have to remember (and specify) parent. hth -- Vlad -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 193 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/scm-migration-dev/attachments/20080818/232deb78/attachment.bin>

[scm-migration-dev] hg backup/restore loses parent

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

[scm-migration-dev] need hook to update hg.os.o

Author: David Marker Repository: /hg/scm-migration/onnv-gk-tools Latest revision: 918a432b1d8bf630c77759097e2d19d8dc801f69 Total changesets: 1 Log message: need hook to update hg.os.o Files: create: hook/updateoso.py update: clone-hgrc update: hook/__init__.py upda

[scm-migration-dev] hg backup/restore loses parent

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

[scm-migration-dev] hg backup/restore loses parent

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

[scm-migration-dev] Reparenting in Mercurial

rmail/scm-migration-dev/attachments/20080818/d62bbfc7/attachment.bin>

[scm-migration-dev] hg backup/restore loses parent

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

[scm-migration-dev] warning about SCCS keywords at "hg pbchk"

Zhijun Fu writes: > usr/src/uts/common/inet/arp.h: 30: contains SCCS keywords "%Z%, %M%, > %I%, %E%" > usr/src/uts/common/inet/arp/arp.c: 27: contains SCCS keywords "%Z%, %M%, > %I%, %E%" > usr/src/uts/common/inet/ip/ip_ire.c: 27: contains SCCS keywords "%Z%, > %M%, %I%, %E%" Those are SCCS keywor

[scm-migration-dev] Switched build machines, now hg fails

Quoth Alan Perry on Fri, Aug 15, 2008 at 02:28:47PM -0700: > What does this message mean? > > > remote: abort: There is no Mercurial repository here (.hg not found)! > > abort: no suitable response from remote hg! > > I set up some hg repositories on one machine and I had no problem doing > hg o

[scm-migration-dev] simple hg questions

Yuan Chu writes: > > hg clone onnv-clone onnv > *** failed to import extension hgext.cdm: Version Mismatch: > Scm expects Mercurial version 1.0, actual version is 0.9.5 <= I can't > find v1.0 SUNWmercurial This likely means that your system is ancient, and needs to be upgraded. Mercurial 1.