🚀 go-pugleaf

Chris Ebenezer wrote:
> 
> R��mi Letot <remi.letot.nospam@advalvas.be> writes:
> : Maybe you should officially contact the core developpers of GCC or the
> : FSF for such a violation.
> 
> Remember that OTOH it could well be a mistake (i.e legal people writing
> the license without any other input), so maybe the quiet chat approach
> would be best.

Till mentionned he did a "quiet chat approach", but had no answer from
them. What is the possibility for such an approach if they simply don't
want to answer ? Contacting the FSF and the GCC "team" doesn't mean hard
actions, it's simply to take advice and signal the violation. They can
then ask Handspring for explanation, and if no answer take more "robust"
action. I don't think the FSF would jump on HS without other attempt to
resolve the conflict and without fair warnings.

-- 

- R�mi -
Remove ".nospam" for mail copies of the answers