Re: renaming remote branches

From: Miles Bader <miles@gnu.org>
Date: Apr 16, 2009, 08:00 UTC
Message-ID: <buoab6h2fko.fsf@dhlpc061.dev.necel.com>
In-Reply-To: <20090416065934.GA20071@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

> In your situation, I would probably do:
>   ssh remote-host 'cd remote-dir && git branch -m OLD NEW'
> but that is not always an option, depending on your setup.

Yup, don't have real ssh access.

Show 10 quoted lines

>> Also, I note that the old name ("OLD") remains in .git/info/refs, both
>> locally and in the remote; is this a problem?  I can update the local
>> .git/info/refs by running "git update-server-info", but I'm not sure how
>> to do in for the remote repo without having a login there...
>
> If you are not sharing your repo over a dumb transport (like http), then
> the contents of .git/info/refs shouldn't matter. If you are, then you
> should enable the post-update hook to run update-server-info after every
> push (i.e., it is not just the deletion that is a problem, but none of
> your pushes is being marked in .git/info/refs).

Hmmm, there's no way to update the hooks without shell access, right...?

[lots of stuff seems undoable without shell access, i.e., changing .git/descriptions; it'd be nice if there was at least some way to frob all this stuff ...]

-Miles

-- 
Accordion, n. An instrument in harmony with the sentiments of an assassin.