From 292886ab8c2555002b9ade0ebf840745e289acfb Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkI9AR8BqG4RPw_Ov2lnDCJWMuM6WMRobQ" Date: Sun, 26 Jan 2014 22:51:30 +0000 Subject: Added a comment: Sorry to just be getting back... --- doc/sync/comment_10_2cd8ab86f498d6f676f859b552f831eb._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/sync/comment_10_2cd8ab86f498d6f676f859b552f831eb._comment (limited to 'doc/sync/comment_10_2cd8ab86f498d6f676f859b552f831eb._comment') diff --git a/doc/sync/comment_10_2cd8ab86f498d6f676f859b552f831eb._comment b/doc/sync/comment_10_2cd8ab86f498d6f676f859b552f831eb._comment new file mode 100644 index 000000000..da4d01965 --- /dev/null +++ b/doc/sync/comment_10_2cd8ab86f498d6f676f859b552f831eb._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkI9AR8BqG4RPw_Ov2lnDCJWMuM6WMRobQ" + nickname="Dav" + subject="Sorry to just be getting back..." + date="2014-01-26T22:51:28Z" + content=""" +The URLs in question in this case were read-only github https URLs. In any case, my problems are solved by what you've already suggested. I think a less error-sounding response to read-only https repos sounds nice! +"""]] -- cgit v1.2.3