Dear git,
git archive, when writing a zip file, has a silent 4GB file size limit (on the
inputs as well as the output), as it doesn’t fully support zip64.
Although a zip archive written by git which is larger than 4GB can be often
still be unzipped, it won’t be fully useable and some tools (e.g
This set of patches works for my test case.
Thanks,
K.
Dear git,
While tracking down a problem with a filesystem shared by Windows and Ubuntu, I
came across the following code in compat/mingw.c (ming_fstat(), also in
do_lstat()):
if (GetFileInformationByHandle(fh, &fdata)) {
buf->st_ino = 0;
buf->st_gid = 0;
> The purpose of these values is to allow to notice a change on the file system
> without going through the actual file data. Duplicating st_mtime would be
> pointless.
Well, I agree with the first statement. I disagree with the 2nd. It’s not
pointless to fix a problem, and in theory the creati
> On Feb 2, 2018, at 1:18 PM, Johannes Schindelin
> wrote:
>
> You cannot assume that the inode numbers are identical between file
> systems/operating systems. That's simply not going to work.
Yes, I agree with you, I cannot assume this, so I checked. In my case, the
inode numbers are indeed i
5 matches
Mail list logo
