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

Re: What's cooking in git.git (topics)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 30, 2006, 12:54 UTC
Message-ID
<Pine.LNX.4.63.0612301350580.19693@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<45965A82.8030903@gmx.net>
Hi,
On Sat, 30 Dec 2006, Raimund Bauer wrote:
> * Johannes Schindelin wrote, On 30.12.2006 12:22:
> > (Of course, the correct thing would not be "git reset --hard", but rather
> > "git diff --ours | git apply -R; git reset", but that's a tad long, no?)
> Then maybe introduce "git reset --ours" which does exactly that?
That is possible.
But does it make sense? 

It is a volatile state, and errors are too easy. So I think it makes sense to have to _ask_ for such a state.

(Having said that, I think that it actually might make sense for bisecting an error where you _need_ a local patch to get it running to begin with.)

Ciao, Dscho

Previous: Raimund Bauer
Message 8 of 8 in “What's cooking in git.git (topics)”
  1. Junio C HamanoDec 29, 2006
  2. Johannes SchindelinDec 29, 2006
  3. Jakub NarebskiDec 29, 2006
  4. Junio C HamanoDec 29, 2006
  5. Nicolas PitreDec 30, 2006
  6. Johannes SchindelinDec 30, 2006
  7. Raimund BauerDec 30, 2006
  8. Johannes SchindelinDec 30, 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.