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

Re: add -e, was Re: What's cooking in git.git (Apr 2009, #02; Sun, 12)

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 14, 2009, 22:31 UTC
Message-ID
<7v7i1m3m1m.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<alpine.DEB.1.00.0904142224030.10279@pacific.mpi-cbg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Actually, I am beginning to hate the idea of having this in add -e, but 
> would prefer it to be in apply ("git apply $PATCH" could -- and should -- 
> complain when not being called with --unidiff-zero and encountering a 
> patch that should (but does not) have common context lines).

I think it already complains by rejecting. The thing is, only "add -e" knows that the patch being fed to apply is potentially manually corrupt by the end user.

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 5 of 6 in “What's cooking in git.git (Apr 2009, #02; Sun, 12)”
  1. Junio C HamanoApr 13, 2009
  2. add -e, was Re: What's cooking in git.git (Apr 2009, #02; Sun, 12)Johannes Schindelin, Apr 14, 2009
  3. Junio C HamanoApr 14, 2009
  4. Johannes SchindelinApr 14, 2009
  5. Junio C HamanoApr 14, 2009
  6. Johannes SchindelinApr 16, 2009

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.