diff options
| -rw-r--r-- | doc/forum/importfeed_loads_files_a_second_time_prepending_a_2__95__/comment_1_1623344457fbe10c464506e41fbac3d8._comment | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/forum/importfeed_loads_files_a_second_time_prepending_a_2__95__/comment_1_1623344457fbe10c464506e41fbac3d8._comment b/doc/forum/importfeed_loads_files_a_second_time_prepending_a_2__95__/comment_1_1623344457fbe10c464506e41fbac3d8._comment new file mode 100644 index 000000000..03b935f4a --- /dev/null +++ b/doc/forum/importfeed_loads_files_a_second_time_prepending_a_2__95__/comment_1_1623344457fbe10c464506e41fbac3d8._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-10-11T15:17:41Z" + content=""" +RSS feeds have unique IDs that are attached to a post in the feed. +They are supposed to be allocated once and remain unchanged. It's not +entirely uncommon for the unique IDs to change (due to broken feed +generation software, changing feed generation software, etc), and then git-annex +thinks this is a new file in the feed, that happens to have the same +title as another file, so it makes up a unique name for it with the "2_". + +Since the alternative is to miss downloading new files from the RSS feed +if they happen to have the same title as a previous file, I think we have +to live with this. + +(git-annex was improved in version 5.20150727 to avoid some cases +of this) +"""]] |