##// END OF EJS Templates
dirstate-tree: Remove newly-empty nodes after removing a `DirstateEntry`...
Simon Sapin -
r47964:47ccab19 default
parent child Browse files
Show More
@@ -379,9 +379,14 b" impl<'on_disk> super::dispatch::Dirstate"
379 379 had_entry: node.entry.take().is_some(),
380 380 had_copy_source: node.copy_source.take().is_some(),
381 381 };
382 // TODO: this leaves in the tree a "non-file" node. Should we
383 // remove the node instead, together with ancestor nodes for
384 // directories that become empty?
382 }
383 // After recursion, for both leaf (rest_of_path is None) nodes and
384 // parent nodes, remove a node if it just became empty.
385 if node.entry.is_none()
386 && node.copy_source.is_none()
387 && node.children.is_empty()
388 {
389 nodes.remove(first_path_component);
385 390 }
386 391 Some(dropped)
387 392 }
@@ -711,6 +711,9 b' Asking specifically for the status of a '
711 711 $ hg rm b
712 712 $ hg status a
713 713 R a
714 $ hg commit -qm '#1'
715 $ hg status a
716 a: $ENOENT$
714 717
715 718 Check using include flag with pattern when status does not need to traverse
716 719 the working directory (issue6483)
General Comments 0
You need to be logged in to leave comments. Login now