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

Re: [RFC/GSoC] Proposal: Make git-pull and git-am builtins

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 25, 2015, 17:54 UTC
Message-ID
<xmqq4mp92c9h.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CACRoPnTL78ZrqPYYNPkNcW7vConHZXZ66z5P2=3HySrtmZKcrg@mail.gmail.com>
Paul Tan <pyokagan@gmail.com> writes:
> I think it's still good to have the ideal in mind though (and whoops I
> forgot to put in the word "ideal" in the text).
Using or not using fork is merely one of the trade-offs we can make.

"If all other things are equal, no fork is better than a fork" is a meaningless statement, as all other things are never equal in real life---doing things internally will have a cost of having to clean up and a risk to get that part wrong, for example. Engineering is a fine balancing act and setting an absolute goal is not a healthy attitude.

Previous: Paul TanNext: Paul Tan
Message 6 of 9 in “[RFC/GSoC] Proposal: Make git-pull and git-am builtins”
  1. Paul TanMar 24, 2015
  2. Paul TanMar 24, 2015
  3. Matthieu MoyMar 24, 2015
  4. Junio C HamanoMar 24, 2015
  5. Paul TanMar 25, 2015
  6. Junio C HamanoMar 25, 2015
  7. Paul TanMar 26, 2015
  8. [RFC/GSoC v2] Proposal: Make git-pull and git-am builtinsPaul Tan, Mar 25, 2015
  9. Sebastian SchuberthMar 25, 2015

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.