I was trying to register a git repo that exist only locally and received the error. mr: cannot determine git url Its easy to reproduce, just create a new git repo... $ mkdir tmp; cd tmp $ git init Try to register it with mr... $ mr register mr: cannot determine git url $ echo $? 1 I have several other repos already registered with mr which all work fine. Though they are all hg based (I'm switching to git though).
John Eikenberry wrote: There is no origin url for the repository. mr register could configure it with a dummy checkout command: [tmp] checkout = no url known for this repository But then what if someone runs mr on a repository that has no origin url, but does have some other remote url? It would be surprising for the above to result, but mr can't go guessing about which other url to use in such a case. So I think it's better that mr register not try to support your case.
Joey Hess wrote: I would have thought that with the connections to the VCS-Home project or just in general this would be a more common setup. Having a repo with no remotes is one of the nice things about DVCs. But no matter. Is there any mr workaround to get it working with a local-only repo? Or is my best option just adding a dummy url entry to my .git/config?
John Eikenberry wrote: An empty stanza like I showed in .mrconfig will work fine, it's just that I don't see a good way to mr register to guess you want that configuration.
Hi, It is not just mrconfig files in local git repo but manually generated ones and bootstrapped ones seems to suffer this problem of chain loading. This may be obvious for expert mr users but it is a bit non-obvious since it require us to fool mr with the shell command ":" (or "true") for update. I suggest to add an entry as attached patch. (Certainly, adding some special option to the "register" command indicating it is a local mrconfig is another way to address this type of issue. But I like to keep mr as simple as possible like now.) Osamu
Hi, It is not just mrconfig files in local git repo but manually generated ones and bootstrapped ones seems to suffer this problem of chain loading. This may be obvious for expert mr users but it is a bit non-obvious since it require us to fool mr with the shell command ":" (or "true") for update. I suggest to add an entry as attached patch. (Certainly, adding some special option to the "register" command indicating it is a local mrconfig is another way to address this type of issue. But I like to keep mr as simple as possible like now.) Osamu