Re: [git-users] Clone thinks origin has a removed branch

2014-03-31 Thread Nelson Efrain A. Cruz
Hi, i think that prune it's what you are asking for, just like Konstantin explain to you: it removes locals refs to remotes branches that no longer exists, once they are removed they will not appear in your repo. 2014-03-31 1:19 GMT-03:00 Fredrik Linder : > > 'git remote prune origin' removes lo

Re: [git-users] Clone thinks origin has a removed branch

2014-03-30 Thread Fredrik Linder
'git remote prune origin' removes local branches -- that's not my issue :-) Thank you though. My issue is that my local repo (clone1) has an incorrect view of my remote (origin), and I don't know to fix that -- beside messing with the internals or re-cloning it. Besides, this happens regardles

Re: [git-users] Clone thinks origin has a removed branch

2014-03-26 Thread Konstantin Khomoutov
On Tue, 25 Mar 2014 13:33:07 -0700 (PDT) Fredrik Linder wrote: [...] > *The another-branch is actually deleted from origin* > *origin/master*> git branch | grep 'another-branch' | wc -l > 0 > > *Fetching the updated info from origin* > *clone1/abranch*> git fetch > *clone1/abranch*> git fetch --

[git-users] Clone thinks origin has a removed branch

2014-03-25 Thread Fredrik Linder
Hello I have an issue with my clone1 repo not being updated w.r.t. what branches origin has: Scenario: *When I push abranch to origin, it triggers a post-receive hook thatdeletes another-branch from origin* *clone1/abranch*> git push *origin/post-receive*> cd $(mktemp -t -d git.post-receive.X