git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] Remove a bogus empty file
Date: Mon, 26 Feb 2024 08:39:52 -0800	[thread overview]
Message-ID: <xmqqedczdvs7.fsf@gitster.g> (raw)
In-Reply-To: <pull.1674.git.1708958183225.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Mon, 26 Feb 2024 14:36:23 +0000")

"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:

> From: Johannes Schindelin <johannes.schindelin@gmx.de>
>
> This file has been added as part of 2232a88ab6b (attr: add builtin
> objectmode values support, 2023-11-16) and most likely serves no
> relevant purpose.
>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
>     Remove a bogus empty file
>     
>     I happened to stumble over this today. It is a regression in v2.44.0,
>     even if admittedly not a terrible one 😉

Indeed.  Thanks for spotting.  Will queue.


> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1674%2Fdscho%2Fremove-bogus-file-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1674/dscho/remove-bogus-file-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/1674
>
>  neue | 0
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  delete mode 100644 neue
>
> diff --git a/neue b/neue
> deleted file mode 100644
> index e69de29bb2d..00000000000
>
> base-commit: 3c2a3fdc388747b9eaf4a4a4f2035c1c9ddb26d0

      reply	other threads:[~2024-02-26 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 14:36 [PATCH] Remove a bogus empty file Johannes Schindelin via GitGitGadget
2024-02-26 16:39 ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqedczdvs7.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).