From 52bad7501a13b860a670167276a743a83ac44e9e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 9 Sep 2015 14:45:57 -0400 Subject: comment --- ...mment_1_c0d442b646dc40d870b10098a0ee5408._comment | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/todo/wishlist:_matching_options_for_branches/comment_1_c0d442b646dc40d870b10098a0ee5408._comment (limited to 'doc') diff --git a/doc/todo/wishlist:_matching_options_for_branches/comment_1_c0d442b646dc40d870b10098a0ee5408._comment b/doc/todo/wishlist:_matching_options_for_branches/comment_1_c0d442b646dc40d870b10098a0ee5408._comment new file mode 100644 index 000000000..d606d80e1 --- /dev/null +++ b/doc/todo/wishlist:_matching_options_for_branches/comment_1_c0d442b646dc40d870b10098a0ee5408._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-09-09T18:34:29Z" + content=""" +It's hard to add this kind of thing to the preferred content expressions. + +First, it would be quite slow to check if a given key +was present in some file in a given branch. There's no index for that +information. + +Second, even if that were implemented, there's no guarantee at all that +different repositories have the same git branches. If repo Foo wants files in +branch B, and repo Bar sees that, and has no branch B, or a different +version of branch B, how is it supposed to know which files to send to +repo Foo? + +So, I can see the use case, but I don't see how preferred content can +support it. +"""]] -- cgit v1.2.3