[Bug 3917] New: Exporting a patch file for a commit does not include 0-byte files that were added in that commit.

[mercurial-bugs at selenic.com]

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

          Priority: normal
            Bug ID: 3917
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Exporting a patch file for a commit does not include
                    0-byte files that were added in that commit.
          Severity: bug
    Classification: Unclassified
                OS: All
          Reporter: KennethRMason at me.com
          Hardware: All
            Status: UNCONFIRMED
           Version: 2.5.4
         Component: Mercurial
           Product: Mercurial

When trying to export a patch for a commit, the resulting patch file doesn't
include files that were added in the commit, whenever those files that were
added are 0-byte files.

Steps to reproduce:

1. Create a new folder and initialize it as an Hg repository.
2. Add some 0-byte file to that folder, and create an initial commit for that
file.
3. Create a second 0-byte file, and create a second commit for that file.
4. In Hg Workbench, right-click on either of those commits, and choose Export
>> Export Patch.
5. Open the resultant patch file in Notepad / any text viewer.
6. Observe that the patch file does not contain any information about the new
files that were added.

It seems like the newly added files should be included. If I exported that
patch and someone else applied it, they wouldn't really be getting the full
changeset, since the new files aren't included.

Note that if I drop to the command line to generate the patch, if I use --git
as a parameter, then the files are correctly listed in the file. It's only a
problem when generating the patch from inside TortoiseHg or from the
command-line without the --git option.

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