From: Dan Carpenter <dan.carpenter@oracle.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Chaitanya Hazarey <c@24.io>,
andrea.merello@gmail.com, Greg KH <gregkh@linuxfoundation.org>,
driverdevel <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
burzalodowa@gmail.com
Subject: Re: [PATCH 2/4] Staging: rtl8192u: r8192U_wx.c Removed all C99 comments
Date: Tue, 3 Jun 2014 21:36:45 +0300 [thread overview]
Message-ID: <20140603183644.GG15585@mwanda> (raw)
In-Reply-To: <CAMuHMdW1YnLVyZbmD0fadc6KX=EcH4CArC1379CDGb9ACm=GbQ@mail.gmail.com>
On Tue, Jun 03, 2014 at 10:12:23AM +0200, Geert Uytterhoeven wrote:
> What do other people think?
In staging we just automatically delete commented code. It's in the git
log if you need it. It always feels much better after the dead code is
gone.
regards,
dan carpenter
next prev parent reply other threads:[~2014-06-03 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 16:11 [PATCH 1/4] Staging: rtl8192u: r8192U_wx.c removed some dead code Chaitanya Hazarey
2014-06-02 16:11 ` [PATCH 2/4] Staging: rtl8192u: r8192U_wx.c Removed all C99 comments Chaitanya Hazarey
2014-06-03 8:12 ` Geert Uytterhoeven
2014-06-03 18:36 ` Dan Carpenter [this message]
2014-06-03 21:34 ` Chaitanya Hazarey
2014-06-03 21:42 ` Greg KH
2014-06-03 21:42 ` Chaitanya Hazarey
2014-06-02 16:11 ` [PATCH 3/4] Staging: rtl8192u: r8192U_wx.c Added a single space for code-style issue Chaitanya Hazarey
2014-06-02 16:11 ` [PATCH 4/4] Staging: rtl8192u: r8192U_wx.c Removed some more commented out dead code Chaitanya Hazarey
2014-06-19 22:15 ` [PATCH 1/4] Staging: rtl8192u: r8192U_wx.c removed some " Greg KH
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=20140603183644.GG15585@mwanda \
--to=dan.carpenter@oracle.com \
--cc=andrea.merello@gmail.com \
--cc=burzalodowa@gmail.com \
--cc=c@24.io \
--cc=devel@driverdev.osuosl.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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