From: Petr Baudis <pasky@suse.cz>
To: Radoslaw Szkodzinski <astralstorm@o2.pl>
Cc: git@vger.kernel.org, Timo Hirvonen <tihirvon@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: git pull fails
Date: Wed, 29 Mar 2006 00:48:07 +0200 [thread overview]
Message-ID: <20060328224807.GC27689@pasky.or.cz> (raw)
In-Reply-To: <200603281700.17233.astralstorm@o2.pl>
Dear diary, on Tue, Mar 28, 2006 at 05:00:11PM CEST, I got a letter
where Radoslaw Szkodzinski <astralstorm@o2.pl> said that...
> On Tuesday 28 March 2006 16:38, Timo Hirvonen wrote yet:
> > Thanks, but forcing everyone to edit their git/remotes/origin file
> > is not very nice solution. I think git-fetch should update refs for the
> > other non-'broken' branches and leave "pu" and "next" refs untouched.
>
> How do you know a non-broken branch from something weird?
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".
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Right now I am having amnesia and deja-vu at the same time. I think
I have forgotten this before.
next prev parent reply other threads:[~2006-03-28 22:48 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 [this message]
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
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=20060328224807.GC27689@pasky.or.cz \
--to=pasky@suse.cz \
--cc=astralstorm@o2.pl \
--cc=git@vger.kernel.org \
--cc=ralf@linux-mips.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.
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).