git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git pull fails

From
Petr Baudis <pasky@suse.cz>
Date
Mar 28, 2006, 22:48 UTC
Message-ID
<20060328224807.GC27689@pasky.or.cz>
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...

Show 6 quoted lines
> 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.
Previous: Radoslaw SzkodzinskiNext: Timo Hirvonen
Message 5 of 10 in “git pull fails”
  1. Timo HirvonenMar 28, 2006
  2. Ralf BaechleMar 28, 2006
  3. Timo HirvonenMar 28, 2006
  4. Radoslaw SzkodzinskiMar 28, 2006
  5. Petr BaudisMar 28, 2006
  6. Timo HirvonenMar 29, 2006
  7. Junio C HamanoMar 29, 2006
  8. Petr BaudisMar 29, 2006
  9. Junio C HamanoMar 29, 2006
  10. Petr BaudisMar 29, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.