From: "David O'Brien" <obrien@FreeBSD.org>
To: gcc@gcc.gnu.org
Subject: repository copy of FreeBSD i386 config file.
Date: Mon, 04 Sep 2000 13:52:00 -0000 [thread overview]
Message-ID: <20000904135248.A46304@dragon.nuxi.com> (raw)
I would like to see gcc/config/i386/freebsd.h,v repository copied to
gcc/config/i386/freebsd-aout.h,v (I have a script to fixup the tags).
I then would like to see gcc/config/i386/freebsd-elf.h [checked out]
copied on top of gcc/config/i386/freebsd.h and committed. Then
gcc/config/i386/freebsd-elf.h put in the Attic by
``cvs rm -f freebsd-elf.h ; cvs ci freebsd-elf.h''.
Doing such repository copies (ie, moving and coping files around w/in the
repository) is documented in the CVS docs.
The purpose is to create a standard naming for FreeBSD configuration
files. FreeBSD's a.out support is now ancient history and we will never
return to it. I will donate configuration bits for FreeBSD/Alpha and
FreeBSD/IA-64 later. There are two other FreeBSD ports in the works. So
a standard setup would really be nice and clean.
Is this acceptable? If not, could I get permission to do it this way:
cvs co gcc/config/i386/freebsd.h
mv gcc/config/i386/freebsd.h gcc/config/i386/freebsd-aout.h
cvs add gcc/config/i386/freebsd-aout.h
cvs ci gcc/config/i386/freebsd-aout.h
cvs co gcc/config/i386/freebsd-elf.h
mv gcc/config/i386/freebsd-elf.h gcc/config/i386/freebsd.h
cvs ci gcc/config/i386/freebsd.h
cvs rm gcc/config/i386/freebsd-elf.h
cvs ci gcc/config/i386/freebsd-elf.h
# add freebsd-aout.h and remove freebsd-elf.h from gcc/po/*
--
-- David (obrien@FreeBSD.org)
next reply other threads:[~2000-09-04 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-04 13:52 David O'Brien [this message]
2000-09-12 5:02 ` Gerald Pfeifer
2000-09-12 7:06 ` Geoff Keating
2000-09-13 20:13 ` David O'Brien
2000-09-17 22:48 ` H . J . Lu
2000-09-12 11:53 ` Richard Henderson
2000-09-12 14:03 ` Marc Espie
2000-09-13 20:23 ` David O'Brien
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=20000904135248.A46304@dragon.nuxi.com \
--to=obrien@freebsd.org \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).