* git fetch with fetch.prune set bug?
@ 2015-11-20 15:19 Peter van der Does
0 siblings, 0 replies; only message in thread
From: Peter van der Does @ 2015-11-20 15:19 UTC (permalink / raw)
To: git
Hi,
Doing the following commands:
$ git config fetch.prune true
$ git co -b bug/bug-1
Switched to a new branch 'bug/bug-1'
$ touch bugfix
$ git add .
$ git commit -a
$ git push --set-upstream origin bug/bug-1
Counting objects: 2, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 242 bytes | 0 bytes/s, done.
Total 2 (delta 1), reused 0 (delta 0)
To git@github.com:petervanderdoes/Testing.git
* [new branch] bug/bug-1 -> bug/bug-1
Branch bug/bug-1 set up to track remote branch bug/bug-1 from origin.
$ git fetch origin bug/bug-1:refs/remotes/origin/bug/bug-1
From github.com:petervanderdoes/Testing
x [deleted] (none) -> origin/bug/bug-1
$ git branch -r
origin/master
$ git branch
* bug/bug-1
master
The branch still exists on the remote repository.
Is it correct that the git fetch deletes the remote reference?
Peter
--
Peter van der Does
GPG key: CB317D6E
Site: http://avirtualhome.com
GitHub: https://github.com/petervanderdoes
Twitter: @petervanderdoes
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-11-20 15:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-11-20 15:19 git fetch with fetch.prune set bug? Peter van der Does
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.