Hey,
On Sun, Mar 28, 2010 at 5:15 AM, Nathan Kinsinger
<[email protected]> wrote:
> On Mar 27, 2010, at 6:10 PM, Pieter de Bie wrote:
>
>> This feels a bit icky to me. Isn't there a more solid way to do this?
>> take git-svn's default behaviour for example, which creates a single
>> branch refs/remotes/git-svn
>
> ...
>
>> I think this also fails with git-svn's refs/remotes/git-svn branch
>
> I don't use git-svn, so a few questions:
>
> Is there always only one svn remote in a repo?
No, there might be multiple. They don't have to be called 'git-svn'
either. It's not limited to git-svn: you might create a custom refspec
that puts a branch in refs/remotes without a remote namespace. The
namespacing of a remote branch is not tied to the name of the remote
itself (e.g. you might have a remote called 'nathan' that puts stuff
in refs/remotes/nate/*)
> Is there any way to tell if any given ref is the/an svn remote?
Sure, read the .git/config file
[svn-remote "svn"]
url = https://llvm.org/svn/llvm-project/llvm/trunk
fetch = :refs/remotes/git-svn
> Does GitX need to disable functions (like merge) when there's an svn remote
> in the repo?
No, merging and rebasing is supported, though it may be a bit quirky
with upstream. The user has to decide that for himself I guess
> Can we move full git-svn support to 0.8.1?
Sure, we can also choose not to support git-svn at all. Just as long
as the repository doesn't break if you have a git-svn branch.
- Pieter
To unsubscribe from this group, send email to gitx+unsubscribegooglegroups.com
or reply to this email with the words "REMOVE ME" as the subject.
