[Bug 6905] New: Pull into a working directory without history

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=6905

            Bug ID: 6905
           Summary: Pull into a working directory without history
           Product: Mercurial
           Version: 6.7.4
          Hardware: PC
                OS: NetBSD
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: Mercurial
          Assignee: bugzilla at mercurial-scm.org
          Reporter: mercurial-bugzilla at campbell.mumble.net
                CC: mercurial-devel at mercurial-scm.org
    Python Version: ---

Suppose I have a large repository with a long history on one machine, and I
have some application that uses the current content of the repository on
another machine.

The application doesn't care about the history.  It just needs to update
periodically from the current snapshot of the repository.

How can I efficiently and reliably update the application?

1. hg clone/pull is not efficient because it downloads all the history.

2. Copying hg archive output from the repository host to the application host
is not efficient because it transfers the entire repository content on each
update, instead of just what has changed.

3. rsync from the working tree on the repository host to the application host
isn't reliable because it doesn't have a mechanism for taking a snapshot from a
particular hg changeset.

(This is in the service of applications built on CVS which simply have a
checkout on the application host and run `cvs update' from time to time -- with
the caveat, of course, that this may not give an atomic snapshot of the
repository owing to CVS semantics.  But, of course, it would be nice for hg to
improve on this, not simply trade efficiency for reliability.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.