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

Re: [PATCH] Fix pulling into the same branch.

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 11, 2005, 09:56 UTC
Message-ID
<Pine.LNX.4.63.0509111153380.32555@wgmdd8.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7vzmr43vix.fsf@assigned-by-dhcp.cox.net>
Hi,
On Fri, 26 Aug 2005, Junio C Hamano wrote:
Show 7 quoted lines
> Come to think of it, it may be cleaner to simply forbid
> fast-forward fetching into the current repository (whether it is
> "git fetch" or "git pull").  At least in your workflow you do
> not do that ever anyway.
> 
> Johannes, what do you think, as the original advocate of "push in
> reverse"?
I'm fine with it.

Although it might make more sense to check for dirty state, and fast-forward only for a clean state (together with a checkout of the new HEAD).

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 7 in “RE: [PATCH] Fix pulling into the same branch.”
  1. Luck, TonyAug 26, 2005
  2. Junio C HamanoAug 27, 2005
  3. Johannes SchindelinSep 11, 2005
  4. Junio C HamanoSep 11, 2005
  5. Linus TorvaldsSep 11, 2005
  6. Junio C HamanoSep 11, 2005
  7. Johannes SchindelinSep 11, 2005

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.