From: Dave Brolley <brolley@redhat.com>
To: Doug Evans <dje@sebabeach.org>
Cc: fche@redhat.com, cgen@sourceware.org
Subject: Re: remove dups from cgen/cpu?
Date: Thu, 09 Jul 2009 17:03:00 -0000 [thread overview]
Message-ID: <4A5622C8.2090601@redhat.com> (raw)
In-Reply-To: <20090709160851.B60D36E3D1@sebabeach.org>
Doug Evans wrote:
> Hi.
>
> I think it's time to remove the duplicates in src/cgen/cpu
> and keep just the copies in src/cpu.
>
> Any objections?
>
> [Are there any that Redhat wants to keep in src/cgen/cpu,
> at least for now?]
>
I have no objections to the removal of duplicates. Although it has been
explained to me several times, I keep forgetting why we needed src/cpu
vs src/cgen/cpu at all.
> [Some files, e.g. sh*, have signficant differences.
> I was going to leave resolving those for another pass,
> and just do the ones with no or simple differences first.]
>
Wrt sh, the work in src/cpu is most up to date.
Dave
next prev parent reply other threads:[~2009-07-09 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 16:09 Doug Evans
2009-07-09 17:03 ` Dave Brolley [this message]
2009-07-12 16:07 ` Doug Evans
2009-07-24 17:53 ` Dave Korn
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=4A5622C8.2090601@redhat.com \
--to=brolley@redhat.com \
--cc=cgen@sourceware.org \
--cc=dje@sebabeach.org \
--cc=fche@redhat.com \
/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).