Hello Nicolas,
On Thu, 2 Jun 2011 23:04:42 +0200
Dechesne, Nicolas n-deche...@ti.com wrote:
Paul
On Thu, Jun 2, 2011 at 9:24 AM, Paul Sokolovsky
paul.sokolov...@linaro.orgwrote:
This is even more interesting, with Google people confirming that
repo --mirror works within some bounds
against git.linaro.org, works well, but
leads to repo error quoted above if run against mirror.
I then googled for known issues with repo --mirror, couldn't find much,
but there're few reports of obscure issues:
http://groups.google.com/group/repo-discuss/browse_thread/thread/b97524988360b029
it executes by setting
REPO_TRACE=1 in the environment. I verified that very same git
command, when run directly against git.linaro.org, works well, but
leads to repo error quoted above if run against mirror.
I then googled for known issues with repo --mirror, couldn't find much,
but there're
Hello Michael,
On Thu, 02 Jun 2011 21:18:44 +1200
Michael Hudson-Doyle michael.hud...@linaro.org wrote:
[]
Once I moved that .git.git repo away, original issue with repo
sync resolved. I have no idea that double-.git repo was created.
Based on the timestamp, it was created first, and later
Paul
On Thu, Jun 2, 2011 at 9:24 AM, Paul Sokolovsky
paul.sokolov...@linaro.orgwrote:
This is even more interesting, with Google people confirming that repo
--mirror works within some bounds and limitations:
http://groups.google.com/group/repo-discuss/browse_thread/thread/401656c3ad0a4a0c
