Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
Subject: Re: cvslog
Date: Tue, 01 Jan 2002 21:24:09 -0800	[thread overview]
Message-ID: <yl1yh9496u.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <m3pu4u21oh.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 01 Jan 2002 04:24:46 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> I think I've found what triggers it.  If I check something in (and I'm
> doing all this via pcl-cvs, if that matters), and I leave the commmit
> message blank, cvslog will infloop until I kill(1) it.

Aha.  Try this patch.

Index: cvslog
===================================================================
RCS file: /afs/ir/cvs/leland/CVSROOT/cvslog,v
retrieving revision 1.25
diff -u -r1.25 cvslog
--- cvslog      30 Dec 2001 22:34:34 -0000      1.25
+++ cvslog      2 Jan 2002 05:23:03 -0000
@@ -343,8 +343,8 @@
 sub parse_message {
     my $data = shift;
     my @message = <STDIN>;
-    shift @message while ($message[0] =~ /^\s*$/);
-    pop @message while ($message[-1] =~ /^\s*$/);
+    shift @message while (@message && $message[0] =~ /^\s*$/);
+    pop @message while (@message && $message[-1] =~ /^\s*$/);
     $$data{message}{text} = [ @message ];
 }

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



  reply	other threads:[~2002-01-02  5:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-01  2:55 cvslog ShengHuo ZHU
2002-01-01  3:07 ` cvslog Russ Allbery
2002-01-01  3:24   ` cvslog Lars Magne Ingebrigtsen
2002-01-02  5:24     ` Russ Allbery [this message]
2002-01-02  5:31       ` cvslog Lars Magne Ingebrigtsen

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=yl1yh9496u.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    /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).