From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: 3.1.5-pws-8: Import to cvs should ignore version.h
Date: Sat, 13 Feb 1999 10:14:07 -0800 [thread overview]
Message-ID: <990213101407.ZM20581@candle.brasslantern.com> (raw)
As of 3.1.something, version.h is a generated file and shouldn't be imported.
I'd have sent this long ago, but I only recently noticed that the dists (even
the "real" 3.1.5) include .cvsignore files.
Index: Src/.cvsignore
diff -ru ../patched/zsh-3.1.5-pws-8/Src/.cvsignore ./Src/.cvsignore
--- ../patched/zsh-3.1.5-pws-8/Src/.cvsignore Mon Feb 8 01:43:29 1999
+++ ./Src/.cvsignore Fri Dec 18 08:43:38 1998
@@ -19,6 +19,7 @@
libzsh.so*
sigcount.h
signames.c
+version.h
zshpaths.h
zshxmods.h
bltinmods.list
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
reply other threads:[~1999-02-13 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=990213101407.ZM20581@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).