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

Re: [PATCH] blame: allow --contents to work with bare repo

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 19, 2023, 21:21 UTC
Message-ID
<xmqqjzuva981.fsf@gitster.g>
In-Reply-To
<CAG1j3zFps5yKwu=DEgkfmZDrzVoRkdeRFMFbq16ZmyOaTXxWeQ@mail.gmail.com>
韩仰 <hanyang.tony@bytedance.com> writes:
> -                setup_work_tree();
> +                if (!sb->contents_from) {
> +                        setup_work_tree();
> +                }
Unwanted {braces} around a single statement.
The patch is severely whitespace damaged and does not apply.

Please check your outgoing mail route and make sure it does not happen when you send out an updated patch. Sending an e-mail to yourself and checking what you received may also work as a way to sanity-check without bombarding other people and the list with a test message.

Thanks.
Previous: 韩仰Next: Han Young
Message 2 of 4 in “blame: allow --contents to work with bare repo”
  1. blame: allow --contents to work with bare repo韩仰, Jul 19, 2023
  2. Junio C HamanoJul 19, 2023
  3. blame: allow --contents to work with bare repoHan Young, Jul 21, 2023
  4. Junio C HamanoJul 21, 2023

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.