Thanks for your suggestion Bastien, but unfortunately it does not directly map to the shortcut that I implemented in my package. In my *old* syntax:

    git:repo::file.txt

file.txt is a search pattern for a *file* with in the symbolic repo "repo" which maps to a real repo through the hash variable my-org-repos. The whole idea was that I wanted to be able to use the symbolic name as a shortcut. In addition file.txt is not the path of a file in the repo, but a search pattern for a file in the repo. In case of duplicates the user is prompted to interactively resolve the file. In addition I would also like to add a search pattern for a string in the file.

My problem is how to merge this syntax with the org-git-link.el which uses the syntax 
git:/home/user/repo/data/results.png::nobelprize
where /home/.../results.png is the name of the path to a file and nobelprize is the name of a tag.

Both my linking and the org-git-linking are two different equally valid use cases. My problem is how to merge both these use cases under a single syntax.

Regards,
Dov

On Thu, Apr 26, 2012 at 17:00, Bastien <bzg@gnu.org> wrote:
Hi Dov,

Dov Grobgeld <dov.grobgeld@gmail.com> writes:

> Thanks for the link. I wasn't aware of that package. I see that I
> have a conflict in syntax as I used double colon for indicating the
> git repo while org-git-link.el used double colon for search pattern.

The double colon is standard in Org for indicating the search pattern,
please use it this way too.

> Thus to join the packages I need to change the syntax. Which of the
> following would make more sense:
>
>    git:@repo:file-in-repo::pattern-in-file
>    git://repo/file-in-repo::pattern-in-file
>
> or perhaps some other syntax? Suggestions?

git:[user@?][repo-server]:[git-repo-itself]::[search-pattern]

When user is set, the repo-server URL won't have a protocol
(git will be used by default as a protocol.)

When user is not set, the repo-server may contain git:// or
http:// as the protocol.

But I didn't test your packing, so I'm maybe shooting in the
dark for this syntax suggestion.

HTH,

--
 Bastien