From: Joey Hess Date: Tue, 25 Jan 2022 16:39:46 +0000 (-0400) Subject: close; out of scope X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~2^2^2~53^2~314 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=28ec94ee7fb080ec31a29fe121f2e94bc68e6fba;p=git-annex.git close; out of scope --- diff --git a/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex__58_____34__Invalid_path_repo__47__.git__47__X__34___for_many_X.mdwn b/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex__58_____34__Invalid_path_repo__47__.git__47__X__34___for_many_X.mdwn index 6c7444afd1..95a04740d7 100644 --- a/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex__58_____34__Invalid_path_repo__47__.git__47__X__34___for_many_X.mdwn +++ b/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex__58_____34__Invalid_path_repo__47__.git__47__X__34___for_many_X.mdwn @@ -35,3 +35,5 @@ I don't know what this error means. Is there a right way to work around this? > [[!meta title="cannot add .git/ to a git repository. even when using git-annex."]] > [[!taglink confirmed]] (but may be out of scope for git-annex) --[[Joey]] +> > +> > [[closing|done]] as out of scope diff --git a/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex__58_____34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_3_3377120e8e246f5ec74d372015590a6c._comment b/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex__58_____34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_3_3377120e8e246f5ec74d372015590a6c._comment new file mode 100644 index 0000000000..9ba55f760a --- /dev/null +++ b/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex__58_____34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_3_3377120e8e246f5ec74d372015590a6c._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2022-01-25T16:39:05Z" + content=""" +I think this is out of scope for git-annex. It's not its place to change +what files git allows to be version controlled. +"""]]