From: Junio C Hamano <junkio@cox.net>
To: Timo Hirvonen <tihirvon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git pull fails
Date: Tue, 28 Mar 2006 16:22:28 -0800 [thread overview]
Message-ID: <7vzmjagkvv.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060329031136.e0389c00.tihirvon@gmail.com> (Timo Hirvonen's message of "Wed, 29 Mar 2006 03:11:36 +0300")
Timo Hirvonen <tihirvon@gmail.com> writes:
> Petr Baudis <pasky@suse.cz> wrote:
>
>> If I understand it right, Timo complains that git-fetch got
>> non-fastforward commits for "pu" and "next" and a good fastforward
>> commit for "master", but it didn't update the ref for ANY head, not even
>> the "master".
>
> Exactly. Maybe git-fetch should abort only if it could not update the
> currently checked out branch?
The erroring-out is there so that the user can take notice.
next prev parent reply other threads:[~2006-03-29 0:22 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 [this message]
2006-03-29 0:24 ` Petr Baudis
2006-03-29 0:40 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vzmjagkvv.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=tihirvon@gmail.com \
/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.
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.