On 2025-05-27 10:09, Mark Millard wrote:
> Alastair Hogge <agh_at_riseup.net> wrote on
> Date: Mon, 26 May 2025 22:58:38 UTC :
> 
>> . . .
>> 
>> GitHub is another Walled Garden. You need an account to read code on
>> it's platform,
> 
> I'm right now using an old iPad with FireFox looking at the
> recent upstream error about fopen("tmp/pkg_add_cache","w")
> still being in use in recent pkg-devel update. I did not
> log into my github account to do this. (Line 1177 of
> pkg_add.c .) The "Sign in" button still says that.
> 
> For reference, I navigated to what ended up
> being:
> 
> github.com/freebsd/pkg/blob/main/libpkg/pkg_add.c
> 
> This is in the USA, in case that matters.
> 
> May be you mean something more specific, but, as far as I
> can tell, your claim above is just false here.

If I point Firefox at
https://github.com/search?q=repo%3Amamedev%2Fmame%20freebsd&type=issues,
on the left side of the site, under "Filter by", there is the following
options:
Code
Issues
Pull requests
Discussions
Commits
Packages
Wikis

To the right of "Code" will be "...", the remaining items in the list,
will have a hit count to the right. Clicking on "Code" takes on to a
"Sign in to search code on GitHub" landing page, this is what I meant,
sorry for the confusion. A super handy feature, locked behind their
Wall.

>> and they are terrible at providing access to new
>> subscribers.
> 
> I've never had troubles that would lead me to such
> a statement --or much of any note. (I do have an
> account  --and have had it for a long time, so,
> likely not matching your specification of "new
> subscribers" at this point. I'm not going to create
> another account to check a better matching context.)
> 
>> I am on my second account, and none of my up upstream
>> Issues are appearing. . . .
>> . . .
> 
> I've never had troubles with my issue submittals on
> github, including the one today about the bug
> referenced above. (Not that I submit such very often.)
> The submittal shows up just fine (#2450).
> 
> 
> ===
> Mark Millard
> marklmi at yahoo.com

Reply via email to