From 6724d1fd6246525e00193a8de66e4a159219cc10 Mon Sep 17 00:00:00 2001 From: matrss Date: Mon, 16 Dec 2024 22:48:16 +0000 Subject: [PATCH] Added a comment --- ...comment_3_48b8108fa3fd16ef72c5beeb0765e5c5._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Requesting_of_files_across_disconnected_devices/comment_3_48b8108fa3fd16ef72c5beeb0765e5c5._comment diff --git a/doc/forum/Requesting_of_files_across_disconnected_devices/comment_3_48b8108fa3fd16ef72c5beeb0765e5c5._comment b/doc/forum/Requesting_of_files_across_disconnected_devices/comment_3_48b8108fa3fd16ef72c5beeb0765e5c5._comment new file mode 100644 index 0000000000..406b747057 --- /dev/null +++ b/doc/forum/Requesting_of_files_across_disconnected_devices/comment_3_48b8108fa3fd16ef72c5beeb0765e5c5._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="matrss" + avatar="http://cdn.libravatar.org/avatar/cd1c0b3be1af288012e49197918395f0" + subject="comment 3" + date="2024-12-16T22:48:16Z" + content=""" +There is a standard group called \"transfer\" which is meant for this kind of thing: . This is especially applicable if there is a static preferred content expression that can be written for each repository (i.e. no ad-hoc gets, just something more structured). + +To make it more dynamic you could include a match on a metadata tag in a repositories preferred content expression. Requesting a file would then be setting the tag on it (well, and a bunch of syncing in all repositories). +"""]]