From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh-workers@sunsite.auc.dk
Subject: CVS again (Re: Module idea to help developers)
Date: Thu, 14 Oct 1999 13:27:17 +0100 [thread overview]
Message-ID: <19991014132717.A12940@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <991014034839.ZM15300@candle.brasslantern.com>
Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
> I agree, but that presupposes a CVS archive, which we've made no progress
> on establishing over the last two or three months that it's been under
> serious consideration. The Sunsite Denmark folks are completely silent
> (I don't think they're even looking at the zsh-*-owner mail right now)
> and PWS is apparently offline for an indeterminate time. I was hoping
> for something quick but effective in the meantime.
I have access to a well-specced and reliable RedHat box with a
high-bandwidth connection in the UK, use of which as a temporary
zsh-workers CVS facility would be welcome. Then when the Sunsite
people re-emerge, it could be moved there if so desired.
Oliver Kiddle (opk@u.genie.co.uk) wrote:
> How do you extract patches from e-mails - I'd be inclined to write a
> filter which takes the message header to grab the message number and
> puts it in a file.
I already did that:
-------- 8< -------- 8< --------
#!/usr/bin/perl -w
use strict;
use Mail::Util qw(read_mbox);
use Mail::Internet;
my $tmp_file = "/tmp/zsh.patch.delivery.$$";
my $dest_dir = '/home/localadams/IN/zsh-patches';
open(TMP, ">$tmp_file") or die $!;
print TMP <>;
close(TMP) or die $!;
my @msgs = read_mbox($tmp_file);
foreach my $msg (@msgs) {
my $mail = new Mail::Internet $msg;
if ($mail->head->get('From ') =~ /^zsh-workers-return-(\d+)/) {
my $id = $1;
my $dest = "$dest_dir/$id";
if (-e $dest) {
warn "File $dest already existed! Skipping ...\n";
}
else {
open(OUT, ">$dest_dir/$id") or die $!;
$mail->print(\*OUT);
close(OUT) or die $!;
}
}
else {
my $subject = $mail->head->get('Subject');
warn "Couldn't get id from message `$subject'; discarding.\n";
}
}
unlink $tmp_file;
exit 0;
-------- 8< -------- 8< --------
(Temp file security risk ignored 'cos I wrote it for my laptop.)
I also automated the rpm-building process.
> It can then also cut out the patch.
Why bother? It's nice to keep the text, and patch extracts the patch
automatically anyway.
> > and PWS is apparently offline for an indeterminate time. I was hoping
> > for something quick but effective in the meantime.
Eek, I hadn't realised.
> If PWS is going to be away for a while then it might help a lot if
> someone else releases an intermediate release.
Agreed. Bart? :-)
> I rarely apply c-code patches because it's not normally a long wait
> to the next pws release but I had wanted to apply a couple of Sven's
> recent patches. I had little success with this so I'll either have
> to get all the patches from the archive or wait.
This should be a good kickstart excuse for getting a CVS repository
into action.
next prev parent reply other threads:[~1999-10-14 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-13 16:20 Module idea to help developers Bart Schaefer
1999-10-13 18:42 ` Clint Adams
1999-10-14 3:48 ` Bart Schaefer
1999-10-14 10:52 ` Oliver Kiddle
1999-10-14 12:27 ` Adam Spiers [this message]
1999-10-15 13:57 ` CVS again (Re: Module idea to help developers) Clint Adams
1999-10-15 14:08 ` Andrej Borsenkow
1999-10-15 14:19 ` Clint Adams
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=19991014132717.A12940@thelonious.new.ox.ac.uk \
--to=adam@thelonious.new.ox.ac.uk \
--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).