[Bug 3632] New: Cloning a repository with largefiles and branching to a new branch adds unchanged largefiles again

[bugzilla-daemon at bz.selenic.com]

http://bz.selenic.com/show_bug.cgi?id=3632

          Priority: normal
            Bug ID: 3632
                CC: mercurial-devel at selenic.com, natosha at gmail.com
          Assignee: bugzilla at selenic.com
           Summary: Cloning a repository with largefiles and branching to
                    a new branch adds unchanged largefiles again
          Severity: bug
    Classification: Unclassified
                OS: Windows
          Reporter: Bastian.Wassermann at multivac.de
          Hardware: PC
            Status: UNCONFIRMED
           Version: unspecified
         Component: largefiles
           Product: Mercurial

When i branch a fresh cloned repository to a new named_branch. Mercurial adds
all largefiles to the new repository, although no file was touched.

Enclosed is the code i tried:

C:\tests>hg clone -uspecific_version %Repository% %workingDir%
updating to branch specific_version
projrc settings file updated and applied
4987 files updated, 0 files merged, 0 files removed, 0 files unresolved
getting changed largefiles
36 largefiles updated, 0 removed

C:\tests>hg branch --force test
marked working directory as branch test
(branches are permanent and global, did you want a bookmark?)

C:\tests>hg commit --addremove -m "test commit"
adding DOC/.*./*.doc
adding DOC/.*./*.doc
adding DOC/.*./*.doc
adding MEDIA/.*./*.mpg
adding TOOLS/.*./*.pdf

C:\tests>hg version
Mercurial Distributed SCM (version 2.3.1)
(see http://mercurial.selenic.com for more information)

Copyright (C) 2005-2012 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

C:\tests>hg push --new-branch -f
pushing to %Repository%
searching for changes
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 0 changes to 34 files (+1 heads)

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