Deutsch English Français Italiano |
<slrnvhukcp.169i.philip@rincewind.trouble.is> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Philip Paeps <philip@trouble.is> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: How to get my port ustreamed? Date: Mon, 28 Oct 2024 16:55:53 +0800 Organization: Happily Disorganized Lines: 23 Message-ID: <slrnvhukcp.169i.philip@rincewind.trouble.is> References: <d59e5a74-1b85-03f7-e33c-4059c86c9604@googlemail.com> <lnc4t1F24ckU1@mid.individual.net> <60965d97-b9c1-00ad-3089-b8282cfb1c1e@googlemail.com> <veqoro$2ncqa$1@dont-email.me> <0c1b48f3-da04-3c03-f353-0d79ba315a87@googlemail.com> <vf1ffm$3qli4$1@dont-email.me> <c56d58b5-3055-f73b-f9b7-d789498363cb@googlemail.com> X-Trace: individual.net wbJHoUqLcTVD+MEg/IgDwwACBhoZ/IHrF90qPVRyiAbp/y/Azr Cancel-Lock: sha1:F4+MOKkwl3hjfJVNmAj8UYlpF+w= sha256:u4lBNN1JwiXctUjP5KyaLbSGjHICbpI4m3ax5eNg+10= X-PGP-Fingerprint: B851 CD3A C248 F2ED 3E2C C18C BB6D 8A14 AFE7 D96B X-Date: Today is Sweetmorn, the 9th day of The Aftermath in the YOLD 3190 X-Phase-of-Moon: The Moon is Waning Crescent (15% of Full) User-Agent: slrn/1.0.3 (FreeBSD) Bytes: 2182 Robin Haberkorn <robin.haberkorn@googlemail.com> wrote: > On Sat, 19 Oct 2024, Alastair Hogge wrote: >>You should have been here when loads of the official mailing lists >>where synchronised here on Usenet, good times...sadly gone now, and >>now, even mailing lists are being replaced by shit like Github, and >>even Matrix has entered the picture. > > Github doesn't really get accepted in the FreeBSD communit it seems. The FreeBSD Project hosts its own Git repositories. >By the way, I am about to patch the kernel to get a job interview with >some company. While the docs say, you can try submitting a PR on >freebsd-src via Github, I was recommened to use reviews.freebsd.org. >That's the way to go? Yes. And put a pointer to your review in bugs.freebsd.org if you're fixing a bug. Discussing changes on mailing lists is also encouraged. hackers@ and current@ are often good places to start. arch@ may be appropriate for broader architectural changes, but probably best to start with hackers@. Philip