Re: [PATCH 2/6] parsemail-batch.sh: pass command-line options to parsemail
Hi Stephen, > > I think this does the same thing as parsearchive? I don't know if this > is still necessary, if so, but as it doesn't cost anything to keep > around for now: If I understand correctly, parsearchive parses a single file containing a bunch of mail, and parsemail parses a directory containing a bunch of files each with one mail. Could be wrong though - haven't looked at parsearchive yet. > > Reviewed-by: Stephen Finucane Thanks! Regards, Daniel ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: [PATCH 2/6] parsemail-batch.sh: pass command-line options to parsemail
On 23 Sep 10:06, Daniel Axtens wrote: > Signed-off-by: Daniel Axtens I think this does the same thing as parsearchive? I don't know if this is still necessary, if so, but as it doesn't cost anything to keep around for now: Reviewed-by: Stephen Finucane ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
[PATCH 2/6] parsemail-batch.sh: pass command-line options to parsemail
Signed-off-by: Daniel Axtens --- patchwork/bin/parsemail-batch.sh | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/patchwork/bin/parsemail-batch.sh b/patchwork/bin/parsemail-batch.sh index 31ef4f0a7e4f..06de3d77ac95 100755 --- a/patchwork/bin/parsemail-batch.sh +++ b/patchwork/bin/parsemail-batch.sh @@ -21,9 +21,9 @@ PATCHWORK_BINDIR=`dirname $0` -if [ $# -ne 1 ] +if [ $# -lt 1 ] then - echo "usage: $0 " >&2 + echo "usage: $0 [options]" >&2 exit 1 fi @@ -37,9 +37,11 @@ then exit 1 fi +shift + ls -1rt "$mail_dir" | while read line; do echo $line - $PATCHWORK_BINDIR/parsemail.sh < "$mail_dir/$line" + $PATCHWORK_BINDIR/parsemail.sh $@ < "$mail_dir/$line" done -- 2.7.4 ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
