Re: remote branches

gt; > > The patch this branch was used for was merged some time ago and I > > > > always initiated to delete the source branch. > > > > > > > > Why is this branch still there? > > > > > > git doesn't delete remote branches on its own, you s

Re: remote branches

branch was used for was merged some time ago and I >> > > always initiated to delete the source branch. >> > > >> > > Why is this branch still there? >> > >> > git doesn't delete remote branches on its own, you should do >> >

Re: remote branches

-a > > > on my local repository I see a plethora of branches like: > > > remotes/origin/dev/harm/cleanup-fret-diagrams.scm > > > > > > The patch this branch was used for was merged some time ago and I > > > always initiated to delete the source branch.

Re: remote branches

harm/cleanup-fret-diagrams.scm > > > > The patch this branch was used for was merged some time ago and I > > always initiated to delete the source branch. > > > > Why is this branch still there? > > git doesn't delete remote branches on its own, you should

Re: remote branches

time ago and I > always initiated to delete the source branch. > > Why is this branch still there? git doesn't delete remote branches on its own, you should do $ git fetch -p origin (short for --prune) once in a while. Jonas signature.asc Description: This is a digitally signed message part

remote branches

Hi, if I do git branch -a on my local repository I see a plethora of branches like: remotes/origin/dev/harm/cleanup-fret-diagrams.scm The patch this branch was used for was merged some time ago and I always initiated to delete the source branch. Why is this branch still there? Cheers, Harm

Re: access to all remote branches

Hi again, On Tue, Mar 11, 2014 at 5:39 PM, David Nalesnik wrote: [...] > Could it be something I need to change in a config file? > > Yes, that was exactly it... Just found this link: http://lists.gnu.org/archive/html/lilypond-devel/2012-02/msg00165.html I ran git config

Re: access to all remote branches

On Tue, Mar 11, 2014 at 5:03 PM, Benkő Pál wrote: > hi, > > > I've had to reinstall LilyDev, and I'm no longer able to see all of the > > remote branches. When I run > > > > git branch -a > > > > I simply see: > > > > dev/loc

Re: access to all remote branches

hi, > I've had to reinstall LilyDev, and I'm no longer able to see all of the > remote branches. When I run > > git branch -a > > I simply see: > > dev/local_working > master > remotes/origin/master you may have cloned only th

access to all remote branches

Hi, I've had to reinstall LilyDev, and I'm no longer able to see all of the remote branches. When I run git branch -a I simply see: dev/local_working master remotes/origin/master Previously I saw branches from the entire history of the project. Unfortunately, I'm drawing a

Re: having trouble fetching all remote branches

Graham Percival writes: > Delete your lilypond directory and start it fresh with a new git > clone. Of course, back up any work you have first by doing git > format-patch origin and double-check that you have the right > patches. > > It is seriously not worth trying to change your .git/config.

Re: having trouble fetching all remote branches

2012/2/7 David Kastrup : > Janek Warchoł writes: > >> My local repository wasn't created with git clone, and i have only one >> remote branch ('origin/master'); i cannot push to staging because of >> that.  I've tried 'git fetch --all', but t

Re: having trouble fetching all remote branches

On Tue, Feb 07, 2012 at 08:51:24AM +0100, Janek Warchoł wrote: > My local repository wasn't created with git clone, and i have only one > remote branch ('origin/master'); i cannot push to staging because of > that. I've tried 'git fetch --all', but the other

Re: having trouble fetching all remote branches

2012/2/7 David Kastrup : > Francisco Vila writes: > >> 2012/2/7 Janek Warchoł : >>> My local repository wasn't created with git clone, and i have only one >>> remote branch ('origin/master'); i cannot push to staging because of >>> tha

Re: having trouble fetching all remote branches

Francisco Vila writes: > 2012/2/7 Janek Warchoł : >> My local repository wasn't created with git clone, and i have only one >> remote branch ('origin/master'); i cannot push to staging because of >> that.  I've tried 'git fetch --all', but the

Re: having trouble fetching all remote branches

2012/2/7 Janek Warchoł : > My local repository wasn't created with git clone, and i have only one > remote branch ('origin/master'); i cannot push to staging because of > that.  I've tried 'git fetch --all', but the other remote branches do > not appea

Re: having trouble fetching all remote branches

Janek Warchoł writes: > My local repository wasn't created with git clone, and i have only one > remote branch ('origin/master'); i cannot push to staging because of > that. I've tried 'git fetch --all', but the other remote branches do > not appea

having trouble fetching all remote branches

My local repository wasn't created with git clone, and i have only one remote branch ('origin/master'); i cannot push to staging because of that. I've tried 'git fetch --all', but the other remote branches do not appear, and i don't see a solution in git fetch