[PATCH] Always apply Zero and Shark patches
Andrew John Hughes
gnu_andrew at member.fsf.org
Fri May 8 08:33:36 PDT 2009
2009/5/8 Gary Benson <gbenson at redhat.com>:
> Andrew John Hughes wrote:
>> 2009/5/8 Gary Benson <gbenson at redhat.com>:
>> > > If so, I'd like to just push them (or rather the 7 equivalents)
>> > > into the IcedTea forest for 7.
>> >
>> > What is the process for going from there to the OpenJDK forest?
>>
>> Same as aph outlined. Having the commits in the IcedTea forest
>> would mean that you could roll the patches/webrev from the
>> changeset(s) there, and we can do 'raw' OpenJDK builds of
>> Zero/Shark. HotSpot in the IcedTea forest will be the same as
>> HotSpot in the master jdk7 tree as soon as I bump to b57.
>
> That's cool. I was a little concerned that they might disappear
> into a mass of changes, but I guess we can pull them out more or
> less painlessly so long as each patch is an individual commit.
>
A patch-->commit relationship was the intention. From such a
changeset, you can do hg diff -g to get a patch to submit upstream,
and the webrev script also requires a changeset rather than a patch.
> Cheers,
> Gary
>
> --
> http://gbenson.net/
>
--
Andrew :-)
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net
PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
More information about the distro-pkg-dev
mailing list