From: Chmouel Boudjnah <chmouel@mandrakesoft.com>
To: mason@primenet.com.au
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: cvs (was: PATCH: completion with rpm and --target)
Date: 17 Apr 2000 01:59:15 -0700 [thread overview]
Message-ID: <m2itxh5cik.fsf_-_@natanya.us.mandrakesoft.com> (raw)
In-Reply-To: mason@primenet.com.au's message of "17 Apr 2000 08:54:30 GMT"
mason@primenet.com.au (Geoff Wing) writes:
> You should be doing "cvs co -P" or "cvs update -dP" anyway if you want to
> have a properly up-to-date tree.
yes right or setup in my ~/.cvsrc :
co -P
update -dP
--
MandrakeSoft Inc http://www.mandrakesoft.com
Pasadena, CA USA. --Chmouel
prev parent reply other threads:[~2000-04-17 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-17 8:13 PATCH: completion with rpm and --target Sven Wischnowsky
2000-04-17 8:17 ` Chmouel Boudjnah
2000-04-17 8:54 ` Geoff Wing
2000-04-17 8:59 ` Chmouel Boudjnah [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=m2itxh5cik.fsf_-_@natanya.us.mandrakesoft.com \
--to=chmouel@mandrakesoft.com \
--cc=mason@primenet.com.au \
--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).