public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH V2] xfs: Comment out unreachable code within xchk_fscounters()
Date: Wed, 7 Jun 2023 00:48:04 -0700	[thread overview]
Message-ID: <ZIA2NLCSw7nVMh6w@infradead.org> (raw)
In-Reply-To: <20230607073757.zwfhie3qbn7mox5i@andromeda>

On Wed, Jun 07, 2023 at 09:37:57AM +0200, Carlos Maiolino wrote:
> The code isn't dead, it's temporarily broken. I spoke with Darrick about
> removing it, but by doing that, later, 'reverting' the patch that removed the
> broken code, will break the git history (specifically for git blame), and I
> didn't want to give Darrick extra work by needing to re-add back all this code
> later when he come back to work on this.
> Anyway, just an attempt to quiet built test warning alerts :)
> I'm totally fine ^R'ing these emails :)

#if 0 is a realy bad thing.  I'd much prefer to remvoe it and re-added
it when needed.  But even if Darrick insists on just disabling it, you
need to add a comment explaining what is going on, because otherwise
people will just trip over the complete undocumented #if 0 with a
completely meaningless commit message in git-blame.  That's how people
dealt with code in the early 90s and not now.

  reply	other threads:[~2023-06-07  7:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 15:11 [PATCH V2] xfs: Comment out unreachable code within xchk_fscounters() cem
2023-06-06 15:17 ` Darrick J. Wong
2023-06-07  6:39 ` Christoph Hellwig
2023-06-07  7:37   ` Carlos Maiolino
2023-06-07  7:48     ` Christoph Hellwig [this message]
2023-06-07  8:48       ` Carlos Maiolino
2023-06-07 14:28         ` Darrick J. Wong
2023-06-07 14:30           ` Christoph Hellwig
2023-06-07 14:53             ` Darrick J. Wong

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=ZIA2NLCSw7nVMh6w@infradead.org \
    --to=hch@infradead.org \
    --cc=cem@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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