All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
	David Airlie <airlied@linux.ie>, Ben Skeggs <bskeggs@redhat.com>,
	Ilia Mirkin <imirkin@alum.mit.edu>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH] nouveau: rename aux.c to auxiliary.c for reviewing it on Windows
Date: Thu, 12 Jun 2014 10:51:35 +0800	[thread overview]
Message-ID: <539915B7.1090606@cn.fujitsu.com> (raw)
In-Reply-To: <1402473247-30468-1-git-send-email-laijs@cn.fujitsu.com>

On 06/11/2014 04:24 PM, Borislav Petkov wrote:
> On Wed, Jun 11, 2014 at 03:53:55PM +0800, Lai Jiangshan wrote:
>> When I tried to review the linux kernel on Windows in my laptop
>> and incidentally found that it failed to open the aux.c.
>>
>> And Microsoft tells me:
>> (http://msdn.microsoft.com/en-us/library/aa365247.aspx)
>>
>>> Do not use the following reserved names for the name of a file:
>>> CON, PRN, AUX, NUL, <snip...>, and LPT9. Also avoid these names
>>> followed immediately by an extension; for example, NUL.txt
>>> is not recommended.
>>
>> The name "aux" is listed above. And it sometimes makes sense to
>> review linux on windows, so we rename the aux.c to auxiliary.c.
> 
> I think you missed April 1st by more than 2 months.
> 

EVERY DAY IS APRIL FIRST if you fool others' convenience.

WARNING: multiple messages have this Message-ID (diff)
From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
	David Airlie <airlied@linux.ie>, Ben Skeggs <bskeggs@redhat.com>,
	Ilia Mirkin <imirkin@alum.mit.edu>,
	<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>
Subject: Re: [RFC PATCH] nouveau: rename aux.c to auxiliary.c for reviewing it on Windows
Date: Thu, 12 Jun 2014 10:51:35 +0800	[thread overview]
Message-ID: <539915B7.1090606@cn.fujitsu.com> (raw)
In-Reply-To: <1402473247-30468-1-git-send-email-laijs@cn.fujitsu.com>

On 06/11/2014 04:24 PM, Borislav Petkov wrote:
> On Wed, Jun 11, 2014 at 03:53:55PM +0800, Lai Jiangshan wrote:
>> When I tried to review the linux kernel on Windows in my laptop
>> and incidentally found that it failed to open the aux.c.
>>
>> And Microsoft tells me:
>> (http://msdn.microsoft.com/en-us/library/aa365247.aspx)
>>
>>> Do not use the following reserved names for the name of a file:
>>> CON, PRN, AUX, NUL, <snip...>, and LPT9. Also avoid these names
>>> followed immediately by an extension; for example, NUL.txt
>>> is not recommended.
>>
>> The name "aux" is listed above. And it sometimes makes sense to
>> review linux on windows, so we rename the aux.c to auxiliary.c.
> 
> I think you missed April 1st by more than 2 months.
> 

EVERY DAY IS APRIL FIRST if you fool others' convenience.


  parent reply	other threads:[~2014-06-12  2:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  7:53 [RFC PATCH] nouveau: rename aux.c to auxiliary.c for reviewing it on Windows Lai Jiangshan
2014-06-11  7:53 ` Lai Jiangshan
2014-06-11  8:24 ` Borislav Petkov
2014-06-12  2:39   ` Lai Jiangshan
2014-06-12  2:39     ` Lai Jiangshan
2014-06-12  2:51 ` Lai Jiangshan [this message]
2014-06-12  2:51   ` Lai Jiangshan

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=539915B7.1090606@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.com \
    --cc=airlied@linux.ie \
    --cc=bp@alien8.de \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imirkin@alum.mit.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.