[PATCH STABLE] largefiles: fix an explicit largefile commit after a remove (issue4969)

Matt Harbison mharbison72 at gmail.com
Sun Jan 24 00:32:57 CST 2016


On Sat, 23 Jan 2016 20:58:00 -0500, Matt Harbison <mharbison72 at gmail.com>  
wrote:

> # HG changeset patch
> # User Matt Harbison <matt_harbison at yahoo.com>
> # Date 1453600277 18000
> #      Sat Jan 23 20:51:17 2016 -0500
> # Branch stable
> # Node ID d07901a07264cc495565bce44eccb7d80afb7a25
> # Parent  4c6053a6b17d682b34fb88bbeb5e94ed9085d900
> largefiles: fix an explicit largefile commit after a remove (issue4969)
>

[snip]

>
> There's still maybe an issue when the largefile is deleted outside of  
> Mercurial:
>
>   $ rm large
>   $ hg ci -m "oops" large
>   large: The system cannot find the file specified
>   nothing changed
>   [1]
>
> That may be OK, since the standin file could have been changed since the  
> last
> commit, and this seems safer since the largefile isn't present to  
> regenerate it.

Actually, this isn't OK, and is fixed by the next series.  This patch  
isn't the cause of the issue though, so whoever queues this patch can drop  
this part.


More information about the Mercurial-devel mailing list