From: Tom Leete <tleete@mountain.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention?
Date: Fri, 20 Apr 2001 23:08:09 -0400 [thread overview]
Message-ID: <3AE0F999.BA288768@mountain.net> (raw)
In-Reply-To: 20010420200859.B5510@flint.arm.linux.org.uk
[Cc: trimmed]
Russell King wrote:
>
[...]
>
> Generally it seems like diff needs to produce one more line of context, and
> most of these problems will go away. Yes, there will still be the odd
> problem, so then it becomes the "how much do you crank the setting" problem.
>
$ diff -6 ...
will give 6 lines of context. patch will understand the output without any
extra help.
Cheers,
Tom
--
The Daemons lurk and are dumb. -- Emerson
WARNING: multiple messages have this Message-ID (diff)
From: Tom Leete <tleete@mountain.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention?
Date: Fri, 20 Apr 2001 23:08:09 -0400 [thread overview]
Message-ID: <3AE0F999.BA288768@mountain.net> (raw)
In-Reply-To: <20010420085148.V13403@opus.bloom.county> <Pine.LNX.4.33.0104201206250.12186-100000@xanadu.home> <20010420125005.B8086@thyrsus.com> <20010420200859.B5510@flint.arm.linux.org.uk>
[Cc: trimmed]
Russell King wrote:
>
[...]
>
> Generally it seems like diff needs to produce one more line of context, and
> most of these problems will go away. Yes, there will still be the odd
> problem, so then it becomes the "how much do you crank the setting" problem.
>
$ diff -6 ...
will give 6 lines of context. patch will understand the output without any
extra help.
Cheers,
Tom
--
The Daemons lurk and are dumb. -- Emerson
next prev parent reply other threads:[~2001-04-21 3:09 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 2:36 [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? Matthew Wilcox
2001-04-20 2:36 ` Matthew Wilcox
2001-04-20 3:00 ` [parisc-linux] " Eric S. Raymond
2001-04-20 3:00 ` Eric S. Raymond
2001-04-20 3:17 ` [parisc-linux] " Matthew Wilcox
2001-04-20 3:17 ` Matthew Wilcox
2001-04-20 4:07 ` [parisc-linux] " james rich
2001-04-20 4:07 ` james rich
2001-04-20 4:19 ` [parisc-linux] " Matthew Wilcox
2001-04-20 4:19 ` Matthew Wilcox
2001-04-20 4:52 ` [parisc-linux] " Albert D. Cahalan
2001-04-20 4:52 ` Albert D. Cahalan
2001-04-20 5:17 ` [parisc-linux] " Rik van Riel
2001-04-20 5:17 ` Rik van Riel
2001-04-20 13:13 ` [parisc-linux] " Alan Cox
2001-04-20 13:35 ` Eric S. Raymond
2001-04-20 13:43 ` Alan Cox
2001-04-20 13:53 ` Eric S. Raymond
2001-04-20 14:03 ` Alan Cox
2001-04-20 14:19 ` Eric S. Raymond
2001-04-20 14:44 ` Alan Cox
2001-04-20 14:59 ` Eric S. Raymond
2001-04-20 15:51 ` Tom Rini
2001-04-20 16:06 ` Jeff Garzik
2001-04-20 16:06 ` Jeff Garzik
2001-04-20 16:15 ` Bob McElrath
2001-04-20 16:21 ` Matthew Wilcox
2001-04-20 19:00 ` Jeff Dike
2001-04-20 19:00 ` Jeff Dike
2001-04-20 18:47 ` Matthew Wilcox
2001-04-20 21:55 ` Jeff Dike
2001-04-20 21:55 ` Jeff Dike
2001-04-20 18:53 ` Jes Sorensen
2001-04-20 16:26 ` Jeff Garzik
2001-04-20 16:26 ` Jeff Garzik
2001-04-20 16:35 ` Nicolas Pitre
2001-04-20 16:35 ` Nicolas Pitre
2001-04-20 16:50 ` Eric S. Raymond
2001-04-20 19:08 ` Russell King
2001-04-21 3:08 ` Tom Leete [this message]
2001-04-21 3:08 ` Tom Leete
2001-04-21 8:53 ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone rmk
2001-04-20 18:20 ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? Tom Rini
2001-04-20 18:48 ` Nicolas Pitre
2001-04-20 18:48 ` Nicolas Pitre
2001-04-20 18:55 ` Tom Rini
2001-04-20 21:19 ` David Woodhouse
2001-04-20 21:19 ` David Woodhouse
2001-04-20 21:24 ` Eric S. Raymond
2001-04-20 21:29 ` David Woodhouse
2001-04-20 21:29 ` David Woodhouse
2001-04-20 21:35 ` Eric S. Raymond
2001-04-20 21:39 ` David Woodhouse
2001-04-20 21:39 ` David Woodhouse
2001-04-21 0:24 ` Eric S. Raymond
2001-04-20 22:53 ` Alan Cox
2001-04-21 0:37 ` Eric S. Raymond
2001-04-21 12:32 ` David Woodhouse
2001-04-21 12:32 ` David Woodhouse
2001-04-23 21:12 ` [patch] fix broken symbols (was Re: OK, let's try ...) Arjan van de Ven
2001-04-21 23:39 ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? Jes Sorensen
2001-04-20 18:50 ` Russell King
2001-04-20 18:50 ` Russell King
2001-04-20 21:23 ` Andreas Dilger
2001-04-21 0:52 ` [parisc-linux] Proposal for better attribution structure Eric S. Raymond
2001-04-21 0:52 ` Eric S. Raymond
2001-04-20 8:19 ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? David Woodhouse
2001-04-20 8:19 ` David Woodhouse
2001-04-20 19:47 ` [parisc-linux] " Eric S. Raymond
2001-04-20 19:47 ` Eric S. Raymond
2001-04-20 20:00 ` [parisc-linux] " Matthew Wilcox
2001-04-20 20:00 ` Matthew Wilcox
2001-04-20 20:13 ` [parisc-linux] " Eric S. Raymond
2001-04-20 20:13 ` Eric S. Raymond
2001-04-20 20:55 ` [parisc-linux] " Alan Cox
2001-04-20 20:55 ` Alan Cox
2001-04-21 6:48 ` [parisc-linux] " Grant Grundler
2001-04-21 14:52 ` Eric S. Raymond
2001-04-20 13:08 ` Alan Cox
2001-04-20 13:18 ` Eric S. Raymond
2001-07-29 10:47 ` Riley Williams
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=3AE0F999.BA288768@mountain.net \
--to=tleete@mountain.net \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@parisc-linux.org \
--cc=rmk@arm.linux.org.uk \
/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.