From 16c2625ad64d8a59b66cbcbe01dd46fc3a8c4dc6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 21 Mar 2017 13:34:52 -0400 Subject: comment --- ...omment_26_a69b4c033d85406675bb70e6996590ce._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/tips/downloading_podcasts/comment_26_a69b4c033d85406675bb70e6996590ce._comment diff --git a/doc/tips/downloading_podcasts/comment_26_a69b4c033d85406675bb70e6996590ce._comment b/doc/tips/downloading_podcasts/comment_26_a69b4c033d85406675bb70e6996590ce._comment new file mode 100644 index 000000000..c884f0569 --- /dev/null +++ b/doc/tips/downloading_podcasts/comment_26_a69b4c033d85406675bb70e6996590ce._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 26""" + date="2017-03-21T17:28:27Z" + content=""" +@ewen importfeed already tracks guids, since 2015. Relevant commit is +[[!commit f95a8c867223b2e17d036d0d3377bf0fc9d3adff]] + +You may well have an +older version of git-annex that didn't do that. But there are probably also +feeds that lack a useful guid, or that even make a change that changes the +guid of an existing item. + +With `git annex metadata`, you can see the `itemid` which is where the guid +is stored. + +PS, please post in [[todo]] when you have a request.. +"""]] -- cgit v1.2.3