mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.5.16
Date: Sat, 18 May 2002 17:44:08 +0200	[thread overview]
Message-ID: <20020518154408.GB11424@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205180051100.3170-100000@penguin.transmeta.com> <20020518092121.A30509@flint.arm.linux.org.uk> <20020518092121.A30509@flint.arm.linux.org.uk> <20020518095125.GC10134@louise.pinerecords.com> <200205181128.OAA26251@infa.abo.fi> <20020518153856.GA8171@merlin.emma.line.org>

> > I guess it still is "$_ =~ s/\[?PATCH\]?\s*//i;", which means
> > that it still is broken. There certainly are several solutions,
> > what do people think of "s/\[?[^\]]*PATCH\]?\W*//i;" ?
> > (Maybe a ^ at the beginning?) 
> 
> Don't guess, look:
> 
>     # kill "PATCH" tag
>     s/^\s*\[PATCH\]//;
>     s/^\s*PATCH//;
>     s/^\s*[-:]+\s*//;
>     # strip trailing colon
>     s/:\s*$//;
>     # kill leading and trailing whitespace for consistent indentation
>     s/^\s+//; s/\s+$//;
> 
> So it should not harm "[ARM PATCH]".
> 
> What we would want is only remove the tag when we have symmetric square
> brackets. What we also want is simplicity to allow for easy maintenance
> and, last but not least, simple, anchored regexps for speed.

Good.
Could you repost the latest version *in plaintext* please?


T.

  reply	other threads:[~2002-05-18 15:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-18  7:57 Linux-2.5.16 Linus Torvalds
2002-05-18  8:05 ` Linux-2.5.16 Aschwin Marsman - aYniK Software Solutions
2002-05-18  8:21 ` Linux-2.5.16 Russell King
2002-05-18  9:51   ` Linux-2.5.16 Tomas Szepe
2002-05-18 11:28     ` Linux-2.5.16 Marcus Alanen
2002-05-18 15:38       ` Linux-2.5.16 Matthias Andree
2002-05-18 15:44         ` Tomas Szepe [this message]
2002-05-18  8:52 ` Linux-2.5.16 mikeH
2002-05-18 18:33   ` Linux-2.5.16 Andrew Morton
2002-05-20  0:33 ` Linux-2.5.16 Roman Zippel
2002-05-20  0:39   ` Linux-2.5.16 Linus Torvalds
2002-05-20  0:47     ` Linux-2.5.16 Linus Torvalds
2002-05-20  1:09       ` Linux-2.5.16 Paul Mackerras
2002-05-20  1:25         ` Linux-2.5.16 Linus Torvalds
2002-05-20 12:43           ` Linux-2.5.16 Paul Mackerras
2002-05-20 16:13             ` Linux-2.5.16 Linus Torvalds
2002-05-20 23:30               ` Linux-2.5.16 David S. Miller
2002-05-20 23:37                 ` Linux-2.5.16 David S. Miller
2002-05-21  1:02                   ` [PATCH] TLB changes (was Re: Linux-2.5.16) David S. Miller
2002-05-20 23:55               ` Linux-2.5.16 Paul Mackerras
2002-05-21  0:18                 ` Linux-2.5.16 Paul Mackerras
2002-05-21  5:10             ` Linux-2.5.16 Linus Torvalds
2002-05-21  5:10               ` Linux-2.5.16 David S. Miller
2002-05-21 16:01                 ` Linux-2.5.16 Linus Torvalds
2002-05-21 16:45                   ` Linux-2.5.16 Linus Torvalds
2002-05-20  1:15       ` Linux-2.5.16 Roman Zippel
2002-05-20  1:20         ` Linux-2.5.16 Linus Torvalds
2002-05-20  4:30       ` Linux-2.5.16 David S. Miller
2002-05-20 22:20       ` Linux-2.5.16 Roman Zippel
2002-05-20 23:36         ` [PATCH] Fix rss accounting Roman Zippel
2002-05-20  1:10     ` Linux-2.5.16 Roman Zippel
2002-05-20 17:57       ` Linux-2.5.16 Linus Torvalds

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=20020518154408.GB11424@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.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

all inboxes | Powered by JetHome®