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

branch.pu.forcefetch

From
PRPavel Roskin <proski@gnu.org>
Date
Dec 27, 2006, 20:31 UTC
Message-ID
<1167251519.2247.10.camel@dv>
Hello!

I'm testing the current git from the master branch, and I like the idea of moving the remotes to the config file, but I think there is a significant omission in the new syntax. There is no way to specify that some branches are fast forward.

For example, I clone the git repository anew, and I try to update it by git-fetch a few days later. I get an error:

* refs/remotes/origin/pu: not updating to non-fast forward branch 'pu'
of git://www.kernel.org/pub/scm/git/git

It would be great to have a "non-fastforward" option in the config file for every branch. I'm thinking about something like:

[branch "pu"]
        forcefetch = 1
It would be even better to initialize such option while cloning.
-- 
Regards,
Pavel Roskin
Next: Jakub Narebski
Message 1 of 14 in “branch.pu.forcefetch”
  1. Pavel RoskinDec 27, 2006
  2. Jakub NarebskiDec 27, 2006
  3. Junio C HamanoDec 27, 2006
  4. Jakub NarebskiDec 27, 2006
  5. Pavel RoskinDec 28, 2006
  6. Junio C HamanoDec 28, 2006
  7. 1/2 core.logallrefupdates: log remotes/ tracking branches.Junio C Hamano, Dec 29, 2006
  8. 2/2 Allow non-fast-forward of remote tracking branches in default cloneJunio C Hamano, Dec 29, 2006
  9. Shawn PearceDec 29, 2006
  10. Johannes SchindelinDec 29, 2006
  11. Pavel RoskinDec 29, 2006
  12. Junio C HamanoDec 29, 2006
  13. Pavel RoskinDec 29, 2006
  14. Shawn PearceDec 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.