From: Bart Schaefer <schaefer@zanshin.com>
To: Adam Spiers <adam@spiers.net>
Cc: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: prompt fun
Date: Mon, 11 Oct 1999 15:47:11 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.9910111529490.31348-100000@aztec.zanshin.com> (raw)
In-Reply-To: <19991011223022.A23117@thelonious.new.ox.ac.uk>
On Mon, 11 Oct 1999, Adam Spiers wrote:
> Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
> >
> > Run the "cvs diff" output through this:
> >
> > sed -e '/^RCS/,/^---/d' -e '/^\+\+\+/d'
>
> What if a line within the hunk begins with `--' or `++' though?
Removed lines beginning with "--" shouldn't be a problem, as there won't
be more than one line beginning with "RCS" for any file, and there must be
a line beginning with "---" above all hunks for each file in either diff
format.
Added lines beginning with "++" would cause patch to fail with a warning
about a malformed diff. I think that's probably a pretty rare occurrence
(since we're almost exclusively patching shell script and C source), but
you could make the pattern more detailed if you're concerned:
-e '/^\+\+\+ .* [0-9]+:[0-9]+:[0-9]+/d'
That forces there to be a space after the "+++" and something that looks
like a time on the line as well. Get as precise as you like ...
prev parent reply other threads:[~1999-10-11 22:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-04 18:40 Adam Spiers
1999-10-04 23:14 ` Bart Schaefer
1999-10-04 23:36 ` Adam Spiers
1999-10-05 1:48 ` Mike Fletcher
1999-10-05 11:31 ` Zefram
1999-10-06 20:58 ` Adam Spiers
1999-10-07 10:43 ` Zefram
1999-10-07 13:29 ` bashprompt license (was Re: PATCH: prompt fun) Adam Spiers
1999-10-07 14:19 ` Bart Schaefer
1999-10-07 15:25 ` Oliver Kiddle
1999-10-07 16:45 ` PATCH: prompt fun Clint Adams
1999-10-07 16:49 ` Zefram
1999-10-07 17:03 ` Clint Adams
1999-10-07 17:06 ` Zefram
1999-10-11 13:19 ` Andrej Borsenkow
1999-10-11 16:39 ` Bart Schaefer
1999-10-11 21:30 ` Adam Spiers
1999-10-11 22:47 ` Bart Schaefer [this message]
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=Pine.LNX.4.10.9910111529490.31348-100000@aztec.zanshin.com \
--to=schaefer@zanshin.com \
--cc=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).