Removing a file is not regarded a change?
Gregory Szorc
gregory.szorc at gmail.com
Fri Jan 13 05:12:39 UTC 2017
On Thu, Jan 12, 2017 at 6:06 PM, Augie Fackler <raf at durin42.com> wrote:
>
> > On Jan 12, 2017, at 1:11 PM, Dr Rainer Woitok <rainer.woitok at gmail.com>
> wrote:
> >
> > added 1 changesets with 0 changes to 0 files
> > 0 files updated, 0 files merged, 1 files removed, 0 files unresolved
> >
> > Maybe it's not a bug, but the last two lines are at least looking rather
> > strange ... :-|
>
> It’s not a bug, even though it’s a little confusing. The file contents
> didn’t change, so there’s no new file revision present, so it doesn’t count
> as a change to the file.
>
> Hopefully that satisfies your curiosity!
>
Anticipating a follow-up question of "could we detect removed files in
order to display an accurate count?" Yes, that is technically possible.
However, since there is no explicit "these files were deleted data," the
client would have to detect that deletion indirectly (essentially by
diffing the lists of files in every received changeset). Unfortunately,
this could be quite expensive on larger repositories and could slow down
pulls noticeably. It's not worth the code complexity nor the risk to
performance for a minor cosmetic win.
For what it's worth, while the counts reported during `hg pull` may not be
totally accurate, the counts reported by `hg update` should be.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20170112/5fd59f32/attachment-0002.html>
More information about the Mercurial
mailing list