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

git remote update -> rejected

From
MGMike Galbraith <efault@gmx.de>
Date
Apr 22, 2008, 09:48 UTC
Message-ID
<1208857733.4695.37.camel@marge.simson.net>
Greetings,

Does anyone know what could lead to this? git doesn't have any trouble (well, hasn't had any yet) with any trees other than x86 and sched-devel. Nobody but little old me seems to be having this trouble...

git is pulled nearly every day, but checking out older versions doesn't make any difference (unless i go too far back of course).

marge:..git/linux-2.6 # git remote update Updating origin Updating linux-next Updating stable Updating x86

>From git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86
 ! [rejected]        latest     -> x86/latest  (non fast forward)
 ! [rejected]        master     -> x86/master  (non fast forward)
 ! [rejected]        testing    -> x86/testing  (non fast forward)
Updating sched-devel
>From git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched-devel
 ! [rejected]        for-akpm   -> sched-devel/for-akpm  (non fast forward)
 ! [rejected]        latest     -> sched-devel/latest  (non fast forward)
 ! [rejected]        master     -> sched-devel/master  (non fast forward)
If I rm/add the remote back, all goes fine... until it says rejected.

marge:..git/linux-2.6 # git remote rm x86 marge:..git/linux-2.6 # git remote add x86 git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git marge:..git/linux-2.6 # git remote update Updating origin Updating linux-next Updating stable Updating sched-devel Updating x86

>From git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86
 * [new branch]      base       -> x86/base
 * [new branch]      for-akpm   -> x86/for-akpm
 * [new branch]      for-linus  -> x86/for-linus
 * [new branch]      latest     -> x86/latest
 * [new branch]      master     -> x86/master
 * [new branch]      origin     -> x86/origin
 * [new branch]      testing    -> x86/testing
marge:..git/linux-2.6 #
Next: Jeff King
Message 1 of 28 in “git remote update -> rejected”
  1. Mike GalbraithApr 22, 2008
  2. Jeff KingApr 22, 2008
  3. Mike GalbraithApr 22, 2008
  4. Jeff KingApr 22, 2008
  5. Johannes SchindelinApr 22, 2008
  6. Jeff KingApr 22, 2008
  7. Johannes SchindelinApr 22, 2008
  8. Jeff KingApr 22, 2008
  9. builtin-remote: resurrect forced updates to tracked branchesJohannes Schindelin, Apr 22, 2008
  10. Junio C HamanoApr 22, 2008
  11. Teemu LikonenApr 22, 2008
  12. Johannes SchindelinApr 22, 2008
  13. Jeff KingApr 22, 2008
  14. Johannes SchindelinApr 22, 2008
  15. Paolo BonziniApr 22, 2008
  16. Teemu LikonenApr 22, 2008
  17. Johannes SchindelinApr 22, 2008
  18. Teemu LikonenApr 22, 2008
  19. Paolo BonziniApr 22, 2008
  20. Johannes SchindelinApr 22, 2008
  21. Paolo BonziniApr 22, 2008
  22. Paolo BonziniApr 22, 2008
  23. Johannes SchindelinApr 22, 2008
  24. Junio C HamanoApr 22, 2008
  25. remote add: disallow --master and --mirror with non-bare repositoriesJohannes Schindelin, Apr 22, 2008
  26. Paolo BonziniApr 22, 2008
  27. Paolo BonziniApr 22, 2008
  28. Johannes SchindelinApr 22, 2008

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.