On 4/15/13, Branko Čibej <[email protected]> wrote: > On 15.04.2013 15:59, Olemis Lang wrote: >> On 4/15/13, Branko Čibej <[email protected]> wrote: >>> On 15.04.2013 11:59, Leho Kraav wrote: [...] >>> >>> https://github.com/apache/bloodhound >>> >>> You may want to clone that instead of using git-svn. The mirror appears >>> to have the complete history. >>> [...]
<ot> @brane : we have been discussing before about connecting the repository browser with the instance of Bloodhound deployed in i.a.o/bh . Now that there's a git clone I wonder whether we could clone it in BH VM and use Git connector instead ? ... at least as long as support for remote svn repositories (i.e. #478) is not available / tested / ... </ot> btw , how often is the git clone updated ? real-time ? > > Let me point out that the SVN history is intact. If you "svn log" > current trunk, you'll find that you'll see all revisions up to r1229643, > when BH trunk was created -- even though it was moved in the meantime. > > If git-svn and hg clone cannot follow SVN history correctly, all I can > say is that there's room for improvement in those tools. > Yes , that's a fact ; as it is that hgsubversion devs are not keen to add this feature because of a reason I do not really understand . Anyway , there's another way to work around this lack of support in hgsubversion conversion tool : hg-git Thanks for the pointer . -- Regards, Olemis.
