linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Rosin <peda@axentia.se>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Wolfram Sang" <wsa@the-dreams.de>,
	linux-i2c@vger.kernel.org,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PULL REQUEST] i2c for 4.13
Date: Thu, 13 Jul 2017 23:41:51 +0200	[thread overview]
Message-ID: <190c2257-8cba-a508-e709-aa096bb97835@axentia.se> (raw)
In-Reply-To: <CA+55aFwe9wgV3714O9t96M+HZYZ-9qR58bENomi-W1BPJ_UyjA@mail.gmail.com>

On 2017-07-13 23:05, Linus Torvalds wrote:
> On Thu, Jul 13, 2017 at 1:57 PM, Peter Rosin <peda@axentia.se> wrote:
>>
>> And if you, like me, sometimes take a peek at the core of several
>> subsystems using emacs, the buffers are either named "core.c<subsys>"
>> or "subsys-core.c". The latter naming is more friendly to tab-completion
>> after ctrl-x b.
> 
> Here's a nickel, Kid. Buy a real editor.

Ahh, thanks for calling me a kid, I think I'll have a shave too.

>    http://i.imgur.com/z96dZ0x.jpg
> 
> If your editor can't show directories, the limitations in your
> environment shouldn't screw over everybody else.

FWIW, I agree that your points made sense. I was just pointing out one
situation were I actually preferred the prefix.

Cheers,
Peter

  reply	other threads:[~2017-07-13 21:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 15:49 [PULL REQUEST] i2c for 4.13 Wolfram Sang
2017-07-12 15:54 ` Wolfram Sang
2017-07-12 17:16 ` Linus Torvalds
2017-07-13  7:56   ` Uwe Kleine-König
2017-07-13 20:57     ` Peter Rosin
2017-07-13 21:05       ` Linus Torvalds
2017-07-13 21:41         ` Peter Rosin [this message]
2017-07-13 10:03   ` Wolfram Sang
2017-07-13 10:50     ` Wolfram Sang
2017-08-09 19:29 Wolfram Sang
2017-08-25 14:30 Wolfram Sang
2017-09-01 21:40 Wolfram Sang

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=190c2257-8cba-a508-e709-aa096bb97835@axentia.se \
    --to=peda@axentia.se \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wsa@the-dreams.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).