From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: make-x.bat
Date: Tue, 18 Dec 2001 11:35:53 +0100 [thread overview]
Message-ID: <vaf7krkvmra.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <adwij1nf.fsf@pille.fqdn.th-h.de> (Frank Haun's message of "Sun, 16 Dec 2001 23:08:52 +0100")
Frank Haun <pille3000@gmx.net> writes:
> It helps to write
>
> if "%2" == "" set copy="false"
>
> before
>
> if "%2" == "copy" set copy=true
> if "%2" == "/copy" set copy=true
>
> is evaluated.
Done.
kai
--
Simplification good! Oversimplification bad! (Larry Wall)
next prev parent reply other threads:[~2001-12-18 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 22:08 make-x.bat Frank Haun
2001-12-17 8:48 ` make-x.bat Frank Schmitt
2001-12-18 10:35 ` Kai Großjohann [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-11 15:19 make-x.bat Frank Haun
2001-11-11 16:18 ` make-x.bat Simon Josefsson
2001-11-11 17:11 ` make-x.bat Frank Schmitt
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=vaf7krkvmra.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).