mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

cleanup

Browse source
This commit is contained in:
Joey Hess 2019-07-08 08:59:25 -04:00
parent 4e3a0e31c4
commit 29aed32b04
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 0 additions and 51 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/news/version_6.20181011/comment_1_e35c359202bac8a1cb39355bfd737153._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 1"
date="2018-10-11T18:59:31Z"
content="""
Can you help me understand the SETURLPRESENT etc change? Why shouldn't these calls update presence information? What information do they update?
"""]]

8
doc/news/version_6.20181011/comment_2_269b29f168ae81e76c1cf6040021540b._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 2"
date="2018-10-11T20:12:08Z"
content="""
Btw, the Hackage page says \"All reported builds failed as of 2018-10-11\" -- not sure if that's a concern.
"""]]

10
doc/news/version_6.20181011/comment_3_b81a8aaebf76a08390243e7943bb79a0._comment
View file

@ -1,10 +0,0 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 3"
date="2018-10-11T20:36:58Z"
content="""
Also, can you check that the git-annex dependencies used in conda-forge are still correct? They haven't been updated in a while.
https://github.com/notestaff/git-annex-feedstock/blob/is-update-to-git-annex-6.20181011-new/recipe/meta.yaml#L18
"""]]

8
doc/news/version_6.20181011/comment_4_957247cc827cc4d2597c01f1f5627d0b._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 4"
date="2018-10-12T00:06:16Z"
content="""
a test failure: https://circleci.com/gh/conda-forge/git-annex-feedstock/116?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
"""]]

17
doc/news/version_6.20181011/comment_5_7dae508c3076b8212f9fdb682180a5ca._comment
View file

@ -1,17 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2018-10-16T15:05:42Z"
content="""
I'm not sure that a release announment is the best place to discuss a wide
variety of topics that only happen to have all been included or be released
to the release?
In fact, I'm pretty sure it's not.
I will say that if you are looking for information about any particular
line from the changelog for a release, a good technique is to run `git
blame CHANGELOG`, find the commit for that line, which is generally the
commit that made the change, and will have significantly more information
in the command message and/or bug report touched by that commit.
"""]