aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-07-19 14:07:31 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-07-19 14:07:31 -0400
commit59a4b5c9c42349cb94a1319de787bef181f8b340 (patch)
treebc90278b1215d4962fe08c2254016966ca99c587
parentb642cb47275f5e98b82203e825d7dd57d571d65e (diff)
further thoughts
-rw-r--r--doc/todo/operate_on_branch_contents.mdwn16
1 files changed, 15 insertions, 1 deletions
diff --git a/doc/todo/operate_on_branch_contents.mdwn b/doc/todo/operate_on_branch_contents.mdwn
index ea715a0e8..f3ad9426f 100644
--- a/doc/todo/operate_on_branch_contents.mdwn
+++ b/doc/todo/operate_on_branch_contents.mdwn
@@ -7,4 +7,18 @@ For example, this would be useful in bare repos to fsck only the master
branch, and not all versions of all keys.
It might be worth allowing a full refspec, so that eg `refs/remotes/*/master`
-or `refs/tags/*` can be operated on.
+or `refs/tags/*` can be operated on. --[[Joey]]
+
+> This should be pretty easy to implement, using `git ls-tree`
+> to enumerate the contents of the ref.
+>
+> The wrinkle is that for --all, the name of each key is shown as it's
+> operated on. But in this case, we want to instead display something like
+> "ref:filename".
+>
+> So, every command that supports --branch (which probably
+> should be all the ones currently supporting --all) will need to be
+> modified, to be provided some new data type that is not FilePath to a
+> work tree file, but something to display while operating on an item.
+>
+> Not a hard change to make, but an extensive one. --[[Joey]]