Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Yuri <yuri@rawbw.com>
Cc: Konstantin Khomoutov <kostix@bswap.ru>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: What is the URL of git's bug tracker?
Date: Thu, 21 Jul 2022 10:39:42 -0700	[thread overview]
Message-ID: <xmqqfsiuicv5.fsf@gitster.g> (raw)
In-Reply-To: <98dc2e8e-58b6-80ad-65da-2bd1cc5dffc2@tsoft.com> (yuri@rawbw.com's message of "Thu, 21 Jul 2022 09:49:22 -0700")

Yuri <yuri@rawbw.com> writes:

> On 7/21/22 03:19, Konstantin Khomoutov wrote:
>> There is none - please read https://git-scm.com/community
>
>
> On 04-09-2021 I reported to this ML the bug that git-2.31.0 printed
> stray messages during 'git stash push' command.
>
>
> git stash push -- x11-toolkits/fltk
> Saved working directory and index state WIP on main: 4c2cc95952a6
> graphics/mesa-devel: update to 21.0.b.4390
> <stdin>:83: space before tab in indent.
>      LIBS="$LIBS -lX11 $X_EXTRA_LIBS"
> <stdin>:84: space before tab in indent.
>      CFLAGS="$CFLAGS $X_CFLAGS"
> <stdin>:85: space before tab in indent.
>      CXXFLAGS="$CXXFLAGS $X_CFLAGS"
> <stdin>:88: space before tab in indent.
>      DSOFLAGS="$X_LIBS $DSOFLAGS"
> <stdin>:89: space before tab in indent.
>      $as_echo "#define USE_X11 1" >>confdefs.h
> warning: squelched 40 whitespace errors
> warning: 45 lines add whitespace errors.
>
>
> Now in git-2.37.1 this bug is still there,
>
>
> Is it forgotten about? Is the fix planned? Is it fixed but not yet released?
>
> It's impossible to say without a bug tracker.
>
>
>
> Yuri

Is there aything to be "fixed" in the first place?  What the
transcript shows is that the user tried to run "git stash push" and
in the process of creating the stash, it noticed whitespace errors
in the files that are being modified and reported, which is not
something that is unexpected.  It does not look like a bug.

At the end, after showing the "warning: 45 lines...", perhaps
something else happened that was not described in the report, like
"the stash was not created"?  If so that may be a bug, but it is
unclear if that is what the complaint is about, so...



  reply	other threads:[~2022-07-21 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21  3:07 What is the URL of git's bug tracker? Yuri
2022-07-21 10:19 ` Konstantin Khomoutov
2022-07-21 16:49   ` Yuri
2022-07-21 17:39     ` Junio C Hamano [this message]
2022-07-21 18:01     ` Konstantin Khomoutov

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=xmqqfsiuicv5.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kostix@bswap.ru \
    --cc=yuri@rawbw.com \
    /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