git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: git pull fails
Date: Tue, 28 Mar 2006 16:40:30 -0800	[thread overview]
Message-ID: <7vu09igk1t.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060329002415.GG27689@pasky.or.cz> (Petr Baudis's message of "Wed, 29 Mar 2006 02:24:15 +0200")

Petr Baudis <pasky@suse.cz> writes:

> If your current branch would really be a remote branch and you simply
> git-fetched, your HEAD would change but not your working tree, and at
> that moment things would become very confusing. Cogito would start
> showing nonsensical stuff for cg-status and cg-diff (as well as
> git-diff-tree HEAD output), but your index would at least still be
> correct so I'm not sure how much attention do tools like git-diff pay to
> it, the level of messup would be proportional to that.

People want to leave tracking branches checked out, especially
when they are not developers but are "update to the latest and
compile the bleeding edge" types.  Support for that mode of
operation was invented long time ago and git-pull knows about
it, and the idea was ported to git-cvsimport recently.

  reply	other threads:[~2006-03-29  0:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 13:28 git pull fails Timo Hirvonen
2006-03-28 14:11 ` Ralf Baechle
2006-03-28 14:38   ` Timo Hirvonen
2006-03-28 15:00     ` Radoslaw Szkodzinski
2006-03-28 22:48       ` Petr Baudis
2006-03-29  0:11         ` Timo Hirvonen
2006-03-29  0:22           ` Junio C Hamano
2006-03-29  0:24           ` Petr Baudis
2006-03-29  0:40             ` Junio C Hamano [this message]
2006-03-29  0:57               ` Petr Baudis

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=7vu09igk1t.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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).