From: Peter van der Does <peter@avirtualhome•com>
To: git@vger•kernel.org
Subject: git fetch with fetch.prune set bug?
Date: Fri, 20 Nov 2015 10:19:22 -0500 [thread overview]
Message-ID: <564F39FA.2030107@avirtualhome.com> (raw)
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
reply other threads:[~2015-11-20 15:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=564F39FA.2030107@avirtualhome.com \
--to=peter@avirtualhome$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox