From: Graham Gower <graham.gower@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Renaming gcc 4.4.0 to 4.4.1
Date: Tue, 04 Aug 2009 09:38:39 +0930 [thread overview]
Message-ID: <4A777C07.4030508@gmail.com> (raw)
In-Reply-To: <20090803205909.GA24609@gmail.com>
Khem Raj wrote:
> Hi
>
> Now that gcc 4.4.1 is out I would like to add the recipe but if gcc
> 4.4.0 is not been used then I would prefer to move gcc 4.4.0 to 4.4.1
> and reduce a few recipes.
Makes sense.
Are there any plans to consolidate the gcc patch directories too? In
particular, there appears to be a lot of duplication between each of
the gcc-4.3.x and gcc-4.4.0 dirs. Among other things, I see...
grg@ubiquitous:~/oe/openembedded/recipes/gcc$ find . -name "svn-updates.dpatch"
./gcc-svn/debian/svn-updates.dpatch
./gcc-4.4.0/debian/svn-updates.dpatch
./gcc-4.3.3/debian/svn-updates.dpatch
./gcc-4.3.1/debian/svn-updates.dpatch
./gcc-4.3.2/debian/svn-updates.dpatch
grg@ubiquitous:~/oe/openembedded/recipes/gcc$ ls -l `find . -name "svn-updates.dpatch"`
-rw-r--r-- 1 grg grg 17668056 2009-07-22 10:57 ./gcc-4.3.1/debian/svn-updates.dpatch
-rw-r--r-- 1 grg grg 17668056 2009-07-22 10:57 ./gcc-4.3.2/debian/svn-updates.dpatch
-rw-r--r-- 1 grg grg 17668056 2009-07-22 10:57 ./gcc-4.3.3/debian/svn-updates.dpatch
-rw-r--r-- 1 grg grg 17668056 2009-07-22 10:57 ./gcc-4.4.0/debian/svn-updates.dpatch
-rw-r--r-- 1 grg grg 17668056 2009-07-22 10:57 ./gcc-svn/debian/svn-updates.dpatch
grg@ubiquitous:~/oe/openembedded/recipes/gcc$ grep -rn "svn-updates.dpatch" .
grg@ubiquitous:~/oe/openembedded/recipes/gcc$
Five copies of an unused 17mb patch?
-Graham
next prev parent reply other threads:[~2009-08-04 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 20:59 Renaming gcc 4.4.0 to 4.4.1 Khem Raj
2009-08-04 0:08 ` Graham Gower [this message]
2009-08-04 6:34 ` Koen Kooi
2009-08-04 23:40 ` Khem Raj
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=4A777C07.4030508@gmail.com \
--to=graham.gower@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.