From: jw schultz <jw@pegasys.ws>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: trivial: reiserfs whitespace
Date: Tue, 28 May 2002 16:10:13 -0700 [thread overview]
Message-ID: <20020528161013.H885@pegasys.ws> (raw)
In-Reply-To: <20020526183128.GA11385@elf.ucw.cz> <20020527024354.GA9510@tapu.f00f.org> <20020525145325.GA16155@conectiva.com.br> <20020528075937.GB1190@stupidest.org>
On Tue, May 28, 2002 at 12:59:37AM -0700, Chris Wedgwood wrote:
> On Sat, May 25, 2002 at 11:53:25AM -0300, Arnaldo Carvalho de Melo wrote:
>
> But doing it slowly, together with other patches, is not a bad
> idea.
>
> Well, in that case is there some kind of bk or command that can be
> made to automagically run to purge white-space from the end
> patches/changesets as they are produced? It would also be nice to
> have hunks such as[1]:
>
> --- 1 Tue May 28 00:56:35 2002
> +++ 2 Tue May 28 00:56:34 2002
> @@ -1 +1 @@
> -
> +
>
> stripped completely as they have no functional value and just add
> bloat patches and such like.
>
> This can be done with CVS but as it works very differently to bk
> (which to be honest I really don't understand very well at all) I'm
> not even sure if the above suggestion is meaningful.
>
> --cw
CW makes an interesting point. Perhaps bk could be
configured to check for / +\t/ and /\s+$/ on changed lines,
and possibly their contigious neighbors, and ask about purging
the superfluous whitespace. Comments Larry?
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2002-05-28 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 18:31 trivial: reiserfs whitespace Pavel Machek
2002-05-27 2:43 ` Chris Wedgwood
2002-05-25 14:53 ` Arnaldo Carvalho de Melo
2002-05-28 7:59 ` Chris Wedgwood
2002-05-28 23:10 ` jw schultz [this message]
2002-05-27 10:33 ` Pavel Machek
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=20020528161013.H885@pegasys.ws \
--to=jw@pegasys.ws \
--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.