Hey joes, do you know anything about the process of actually sending the 
packages upstream to ubuntu or debian?


> On Sep 16, 2016, at 3:10 PM, Kevin Choi <code.kc...@gmail.com> wrote:
> 
> Oops nvm. they are both meaning this swift
> 
> On Fri, Sep 16, 2016 at 11:08 AM, Kevin Choi <code.kc...@gmail.com 
> <mailto:code.kc...@gmail.com>> wrote:
> Huh. Surprised there is no trademark issues.
> 
> aha, I see why.
> http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4801:djnmx6.2.40 
> <http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4801:djnmx6.2.40>
> http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4801:djnmx6.2.41 
> <http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4801:djnmx6.2.41>
> 
> I guess apple-swift would be following the trademark. Not sure what the 
> OpenSrc community thinks.
> -Kevin
> 
> On Thu, Sep 15, 2016 at 10:40 PM, Guillaume DIDIER via swift-dev 
> <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
> In either case swift-lang / swiftlang evokes the swift parallel language, not 
> apple's one.
> 
> A solution to avoid ambiguity would be to use apple[-]swift or a variation of 
> it.
> 
> Guillaume DIDIER
> —
> ÉCOLE POLYTECHNIQUE
> 91128 PALAISEAU CEDEX <>
> M. +33 ( <tel:+33%207%C2%A070%2043%2018%2040>0 
> <tel:+33%207%C2%A070%2043%2018%2040>)7 <tel:+33%207%C2%A070%2043%2018%2040> 
> 70 43 18 40 <tel:+33%207%C2%A070%2043%2018%2040>
> guillaume.did...@polytechnique.edu 
> <mailto:guillaume.did...@polytechnique.edu?subject=>
> www.polytechnique.edu <http://www.polytechnique.edu/>
> —
> PS : resent with the right e-mail alias.
> 
> Le 16 sept. 2016 à 00:29, Paulo Faria via swift-dev <swift-dev@swift.org 
> <mailto:swift-dev@swift.org>> a écrit :
> 
>> maybe “swiftlang” is better?
>> 
>> 
>>> On Sep 14, 2016, at 7:09 PM, Richard Neese via swift-dev 
>>> <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
>>> 
>>> Ok so well pkgs would have to be swift-lang-corelibs-foundation 
>>> swift-lang-corelibs-libdispatch and soforth. 
>>>  
>>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 
>>> 10
>>>  
>>> From: Jeff Hajewski via swift-dev <mailto:swift-dev@swift.org>
>>> Sent: Wednesday, September 14, 2016 4:51 PM
>>> To: Ron Olson <mailto:tachokni...@gmail.com>
>>> Cc: swift-dev@swift.org <mailto:swift-dev@swift.org>
>>> Subject: Re: [swift-dev] Debian/Ubuntu Package
>>>  
>>> Agreed on 'swift-lang'. It doesn't seem like a big issue that 'swift' is 
>>> already taken.
>>>  
>>> Jeff
>>>  
>>> On Wed, Sep 14, 2016 at 3:20 PM, Ron Olson via swift-dev 
>>> <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
>>> I am planning on doing something similar with Fedora and figured to call it 
>>> 'swift-lang', as that seems to be available. 
>>> Ron 
>>> On 14 Sep 2016, at 15:16, Richard Neese via swift-dev wrote: 
>>> The issue is there is already a pkg called swift that is nothing to do with 
>>> the apple language.
>>>  
>>>  
>>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 
>>> 10
>>>  
>>> From: Paulo Faria via swift-dev <mailto:swift-dev@swift.org>
>>> Sent: Wednesday, September 14, 2016 1:48 PM
>>> To: swift-dev@swift.org <mailto:swift-dev@swift.org>
>>> Subject: [swift-dev] Debian/Ubuntu Package
>>>  
>>> Hello everyone!
>>>  
>>> Now that Swift 3 is released I think it would be excellent to the community 
>>> if swift became an official debian/ubuntu package. This way we could 
>>> install swift by just doing:
>>>  
>>> apt-get install swift
>>>  
>>> I’d like to know if there’s anyone working on this already. If not, I’d 
>>> love to take the job. I haven’t done this task before so I’d have to find 
>>> out how as I go, so if anyone has any experience with this, I’d love to get 
>>> some directions. Thanks!
>>>  
>>> Cheers,
>>> Paulo
>>> _______________________________________________
>>> swift-dev mailing list
>>> swift-dev@swift.org <mailto:swift-dev@swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-dev 
>>> <https://lists.swift.org/mailman/listinfo/swift-dev>
>>>  
>>>  
>>> 
>>> <ACB4CA7151EF4CE683249621F8A29D07.png>
>>>  <https://www.avast.com/antivirus>  
>>> This email has been checked for viruses by Avast antivirus software. 
>>> www.avast.com <https://www.avast.com/antivirus>
>>>  
>>> _______________________________________________ 
>>> swift-dev mailing list 
>>> swift-dev@swift.org <mailto:swift-dev@swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-dev 
>>> <https://lists.swift.org/mailman/listinfo/swift-dev>
>>> 
>>> _______________________________________________
>>> swift-dev mailing list
>>> swift-dev@swift.org <mailto:swift-dev@swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-dev 
>>> <https://lists.swift.org/mailman/listinfo/swift-dev>
>>>  
>>>  
>>> 
>>> 
>>>  <https://www.avast.com/antivirus>  
>>> This email has been checked for viruses by Avast antivirus software. 
>>> www.avast.com <https://www.avast.com/antivirus>
>>> <ACB4CA7151EF4CE683249621F8A29D07.png>_______________________________________________
>>> swift-dev mailing list
>>> swift-dev@swift.org <mailto:swift-dev@swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-dev 
>>> <https://lists.swift.org/mailman/listinfo/swift-dev>
>> 
>> _______________________________________________
>> swift-dev mailing list
>> swift-dev@swift.org <mailto:swift-dev@swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-dev 
>> <https://lists.swift.org/mailman/listinfo/swift-dev>
> 
> _______________________________________________
> swift-dev mailing list
> swift-dev@swift.org <mailto:swift-dev@swift.org>
> https://lists.swift.org/mailman/listinfo/swift-dev 
> <https://lists.swift.org/mailman/listinfo/swift-dev>
> 
> 
> 

_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Reply via email to