Re: error pushing stash ?

From: Shawn O. Pearce <spearce@spearce.org>
Date: Oct 7, 2008, 00:40 UTC
Message-ID: <20081007004051.GA18889@spearce.org>
In-Reply-To: <20081007003435.GZ5774@eratosthenes.cryptobackpack.org>

David Bryson <david@statichacks.org> wrote:

> [remote "backup"]

...

Show 16 quoted lines

>     mirror = 1
> 
> Only to find some odd error messages:
> 
> $ git push backup
> Counting objects: 133, done.
> Compressing objects: 100% (109/109), done.
> Writing objects: 100% (109/109), 31.25 KiB, done.
> Total 109 (delta 82), reused 0 (delta 0)
> error: refusing to create funny ref 'refs/stash' remotely
> To /users/dbryson/backup/janus.git/
>    549f8a4..8e93d51  8654 -> 8654
>    ef6195b..549f8a4  origin/8654 -> origin/8654
>  + 623e7cb...63d7262 origin/master -> origin/master (forced update)
>  ! [remote rejected] refs/stash -> refs/stash (funny refname)
> error: failed to push some refs to '/users/dbryson/backup/janus.git/'

refs/stash is a funny refname because it contains only 1 '/'. Normally a valid ref has at least 2 '/', e.g. refs/heads/8654 or refs/tags/v1.0.

Naming the stash refs/stash was perhaps funny in the first place since it cannot be moved about on the transport protocol, but then again the bulk of the stash data is actually in the reflog for the stash (and not the stash ref itself) so there is basically no point in pushing or fetching a stash directly.

-- 
Shawn.