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

Re: [PATCH] git-commit --allow-empty

From
Nicolas Pitre <nico@cam.org>
Date
Dec 3, 2007, 17:58 UTC
Message-ID
<alpine.LFD.0.99999.0712031255560.9605@xanadu.home>
In-Reply-To
<7v63zgkw0x.fsf@gitster.siamese.dyndns.org>
On Mon, 3 Dec 2007, Junio C Hamano wrote:
Show 5 quoted lines
> +--allow-empty::
> +	Usually recording a commit that has the exact same tree as its
> +	sole parent commit and the command prevents you from making such
> +	a mistake.  This option bypasses the safety, and is primarily
> +	for use by foreign scm interface scripts.
The first sentence is rather buggy I would say.
Nicolas
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 8 in “hg-to-git: handle an empty dir in hg by combining git commits”
  1. hg-to-git: handle an empty dir in hg by combining git commitsMark Drago, Dec 1, 2007
  2. Junio C HamanoDec 1, 2007
  3. git-commit --allow-emptyJunio C Hamano, Dec 3, 2007
  4. git-commit --allow-emptyJunio C Hamano, Dec 3, 2007
  5. Nicolas PitreDec 3, 2007
  6. Junio C HamanoDec 3, 2007
  7. Junio C HamanoDec 5, 2007
  8. Mark DragoDec 6, 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.