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

close already fixed bug

Browse source 
and document it in the changelog for the release where it was fixed
This commit is contained in:
Joey Hess 2020-03-02 13:47:47 -04:00
parent f9a116f056
commit c578e8ebfd
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
CHANGELOG
View file

@ -57,6 +57,7 @@ git-annex (7.20200226) upstream; urgency=high
on those remotes without encrypting it.
If your remotes are affected, you will want to make sure to delete
any content that git-annex has stored on them that is not encrypted!
* initremote: Fix regression in parsing the exporttree= parameter.
* info: Fix display of the encryption value.
(Some debugging junk had crept in.)
* Bugfix to getting content from an export remote with -J, when the

2
doc/bugs/git-annex__58___Unexpected_parameters__58___exporttree.mdwn
View file

@ -49,3 +49,5 @@ local repository version: 7
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes!
> [[fixed|done]] --[[Joey]]

11
doc/bugs/git-annex__58___Unexpected_parameters__58___exporttree/comment_1_059d50419385a16fbddc96d85debb439._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-03-02T17:20:36Z"
content="""
This was already fixed in git-annex 7.20200226, it turns out.
Some changes required to deal with a related reversion fixed it in passing.
(Note that exporttree=no is the default, so there should
be no need to specify it.)
"""]]