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

Re: [PATCH] Implement git commit as a builtin command.

From
Karl Hasselström <kha@treskal.com>
Date
Nov 2, 2007, 09:42 UTC
Message-ID
<20071102094249.GB30468@diana.vm.bytemark.co.uk>
In-Reply-To
<7vsl3p3s48.fsf@gitster.siamese.dyndns.org>
On 2007-11-02 02:37:43 -0700, Junio C Hamano wrote:
Show 10 quoted lines
> Karl Hasselström <kha@treskal.com> writes:
>
> > I wonder if it would be such a bad idea to make this the default.
> > It seems like _everyone_ who should be using it forget it. And the
> > number of patches made for human or git consumption is probably
> > vastly larger than the number of patches made for consumption by
> > other tools.
>
> On this mailing list, we can pretty much assume that renaming diff
> can be applied by people. But outside world is a different story.

So I guess a prerequisite for this is to get git patch format support into GNU patch, then? :-)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 8 in “Implement git commit as a builtin command.”
  1. Implement git commit as a builtin command.Kristian Høgsberg, Nov 1, 2007
  2. Jakub NarebskiNov 1, 2007
  3. Karl HasselströmNov 2, 2007
  4. Junio C HamanoNov 2, 2007
  5. Karl HasselströmNov 2, 2007
  6. Junio C HamanoNov 1, 2007
  7. Junio C HamanoNov 1, 2007
  8. Kristian HøgsbergNov 2, 2007

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.