git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Andreas Heiduk <andreas.heiduk@mathema.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Bug^Feature? fetch protects only current working tree branch
Date: Sun, 23 Jul 2017 15:13:16 -0700	[thread overview]
Message-ID: <xmqqo9saer9f.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <cb957174-5e9a-5603-ea9e-ac9b58a2eaad@mathema.de> (Andreas Heiduk's message of "Sun, 23 Jul 2017 16:50:54 +0200")

Andreas Heiduk <andreas.heiduk@mathema.de> writes:

> A `git fetch . origin/master:master` protects the currently checked out 
> branch (HEAD) unless the `-u/--update-head-ok` is supplied. This avoids a
> mismatch between the index and HEAD. BUT branches which are HEADs in other
> working trees do not get that care - their state is silently screwed up.
>
> Is this intended behaviour or and just an oversight while implementing
> `git worktree`?

The latter.  "git worktree" is an interesting feature and has
potential to become useful in wider variety of workflows than it
currently is, but end users should consider it still experimental as
it still is with many such small rough edges like this one.

Patches to help improving the feature is of course very welcome.

  reply	other threads:[~2017-07-23 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-23 14:50 Bug^Feature? fetch protects only current working tree branch Andreas Heiduk
2017-07-23 22:13 ` Junio C Hamano [this message]
2017-07-24 21:51   ` Andreas Heiduk

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqo9saer9f.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=andreas.heiduk@mathema.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).