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

Re: Creating empty commits with --intent-to-add

From
Duy Nguyen <pclouds@gmail.com>
Date
Jun 5, 2016, 03:15 UTC
Message-ID
<CACsJy8A8-RgpYxYsJBaLrMia7D3DfQPr4cxASNsaLyCnmgm3ZQ@mail.gmail.com>
In-Reply-To
<fdf86f73-0885-7191-2932-f10feba0bdfc@virtuell-zuhause.de>

On Sun, Jun 5, 2016 at 12:54 AM, Thomas Braun <thomas.braun@virtuell-zuhause.de> wrote:

Show 15 quoted lines
> Hi,
>
> the following procedure
>
> mkdir test
> cd test
> git init
> echo 1 >file
> git add --intent-to-add file
> git commit -m "blurb"
>
> results in a commit. I would have expected that git commit complains,
> as I have not pased the --allow-empty option.
>
> Is that intended behaviour?
It's a bug. I'll get to it very soon.
-- 
Duy
Previous: Thomas BraunNext: Thomas Braun
Message 2 of 3 in “Creating empty commits with --intent-to-add”
  1. Thomas BraunJun 4, 2016
  2. Duy NguyenJun 5, 2016
  3. Thomas BraunJun 5, 2016

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.