From: Ruedi.Hofer@ascom.ch
To: linuxppc-embedded@lists.linuxppc.org
Cc: host@linux01.hasler.ascom.ch
Subject: CVS
Date: Mon, 15 May 2000 11:08:34 +0100 (CED) [thread overview]
Message-ID: <0FUL00C4EG2IEL@pmdf-it.hasler.ascom.ch> (raw)
Hi
I have a slightly off topic question: How do you control your Linux files?
I tried to use CVS and wanted to keep all files stored in there. I imported
directories containing complete Linux distributions....
I ran into problems with those files:
- /dev/xxx
- binary, executable files
I need ideas, scripts
- How to preserve the permissions for the /dev and executable files.
(The PRESERVEPERMISSIONS switch is too strong and complains
about 'hard linkage errors' when rebuilding binaries and committing
to the repo again!)
- How to distinguish automatically between binaries and text files.
(Automatic control of the -kb switch!)
Cheers,
Ruedi Hofer
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-05-15 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-15 10:08 Ruedi.Hofer [this message]
2000-05-15 22:49 ` CVS Pavel Roskin
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=0FUL00C4EG2IEL@pmdf-it.hasler.ascom.ch \
--to=ruedi.hofer@ascom.ch \
--cc=host@linux01.hasler.ascom.ch \
--cc=linuxppc-embedded@lists.linuxppc.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).