Removing => 0 changes to 0 files

[Arne Babenhauserheide]

Am Freitag, 30. November 2012, 08:58:28 schrieb Bryan O'Sullivan:
> On Fri, Nov 30, 2012 at 1:05 AM, gideon <voldermort at hotmail.com> wrote:
> > Removed files don't seem to be included in the summary given by push. If I
> > remove 1 file, I get "remote: added 1 changesets with 0 changes to 0
> > files".
> > Is this correct?
> 
> It's not "correct" exactly, but it is expected. Deleting a file amounts to
> removing its entry from the manifest, and nothing more; the actual file
> data remains untouched. Turning that information into a "we deleted a file"
> message is too expensive to be worth the trouble.

How come that that is expensive?

All information we need is available locally, so accessing it should be an 
order of magnitude faster than transferring the pushed changesets.

It should just require:

    for ctx in $transferred; do
        hg status --removed --change $ctx
    done | wc -l

(and that’s the crudest way I could access this information…)

Is that speed difference actually worth the inconsistency in the user 
interface? I already hit that issue, too, but ignored it - though it surprised 
me and got me to prod again that my most current changeset is correct.

Best wishes,
Arne
--
Ein Würfel System - einfach saubere Regeln: 

- http://1w6.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121130/99243eb4/attachment.asc>