Re: [9front] git/push with refs not in refs/heads

[ori@eigenstate.org]

Quoth Anthony Martin <ality@pbrane.org>:
> Is there interest in allowing git/push to send an
> arbitrary ref to a remote repository? Right now
> the ref has to be a branch in refs/heads.
> 
> My usual way of working with git on Unix is to have
> a canonical origin that I fetch from and a single
> local branch that I commit to and rebase onto the
> origin before pushing.
> 
> Sometimes I want to push the current origin branch
> to a mirror without involving any of my local refs,
> something like:
> 
> 	git push mirror origin/master:master
> 
> where the local refs are
> 
> 	refs/heads/master
> 	refs/remotes/mirror/master
> 	refs/remotes/origin/HEAD
> 	refs/remotes/origin/master
> 
> the remote refs on mirror are
> 
> 	HEAD
> 	refs/heads/master
> 
> and my own master has diverged from origin/master.
> 
> Please advise.
> 
> Thanks,
>   Anthony
> 

That's definitely not supported, but adding
it should be easy.

Git/push -b passes the branch unmolested
to git/send, but git/send assumes that the
ref is under refs/heads.

I think we would adopt the ':' separated
branches in git/send; the main change would
be in send.c:/^readours, where the branch
would have to be split on ':', the lhs resolved,
and the rhs converted to the refs/heads/$remote
format.