ow this same general approach:
>
>(a) to gather all common files into 'harmony/enhanced/trunk' and
> point symbolic links to them.
>
>(b) Add a 'harmony/enhanced/trunk/COPYRIGHT.foo' file containing
>their prior copyr
lic
link 'foo/THIRD_PARTY_NOTICES.txt' to point to that addition,
or add a file by that name containing _only_ the new
information and language referring to the global one.
(Comments?)
(12) Suggest replacing the name 'THIRD_PARTY_NOTICES.txt
ld
> be glad to put it together shortly and submit for The List's
> inspection and approval. What do you say?
>
>
> Dan Lydick
>
>
>> [Original Message]
>> From: Geir Magnusson Jr <[EMAIL PROTECTED]>
>> To:
>> Date: 7/20/06 2:07:14 PM
&
ydick
> [Original Message]
> From: Geir Magnusson Jr <[EMAIL PROTECTED]>
> To:
> Date: 7/20/06 2:07:14 PM
> Subject: [general] centralization of the NOTICE, COPYRIGHT, etc files
>
> If you haven't guessed from my random checkins, questions, and
> befuddlement, I&#x
If you haven't guessed from my random checkins, questions, and
befuddlement, I'm finishing off a first cut at a federated build.
The plan is to cut a hdk and a jre snapshot. The HDK will contain the
jre, but I thought it would be more conventional for users to get a
plain jre and not have to figu
