[GitHub] McFoggy commented on issue #74: [SCM-885] third implementation
McFoggy commented on issue #74: [SCM-885] third implementation URL: https://github.com/apache/maven-scm/pull/74#issuecomment-390914512 I'll do a what I can do to cleanup the git internals but honestly what you call _bloat_ is just the result of a pure `git clone --bare`. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] McFoggy commented on issue #74: [SCM-885] third implementation
McFoggy commented on issue #74: [SCM-885] third implementation URL: https://github.com/apache/maven-scm/pull/74#issuecomment-390867101 Hi Mickael, was of for some days and could not answer before. > Why did you rename the test repo and have added a new one? Unless I did a mistake, I did not touch the existing one. But I have provided a new one in order to have known commits with a documentation on how the repo was built. We are talking about integration tests ; I do not see a problem in providing more controlled ones. The repo is a direct result of a `git clone --bare`. I did not removed or added any files from the built bare repository. I'll amend the PR to take your other remarks into account. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] McFoggy commented on issue #74: [SCM-885] third implementation
McFoggy commented on issue #74: [SCM-885] third implementation URL: https://github.com/apache/maven-scm/pull/74#issuecomment-390867101 Hi Mickael, was of for some days and could not answer before. > Why did you rename the test repo and have added a new one? Unless I did a mistake, I did not touch the existing one. But I have provided a new one in order to have known commits with a documentation on how the repo was built. We are talking about integration tests ; I do not see a problem in providing more controlled ones. The repo is a direct result of a `git clone --bare`. I did not removed or added any files from the built bare repository. I'll amend the PR to take your other remarks into account. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services