jomar

6 ms·

1.
by jomar 14d ago
> Except nobody uses the .us tld This is a bug, not a feature.
2.
by jomar 5mo ago
Indeed. Back in 2018 and 2019 I expended a fair amount of time and energy reporting a squash 'n' merge metadata rewriting bug to GitHub and advocating for the behaviour to be changed. [1] Once or twice someone internal to GitHub g
3.
by jomar 5mo ago
Apparently it's about as expected for a southern giant pouched rat. But he was indeed a particularly good one!
4.
by jomar 7mo ago
> I think even the development system wasn't free either. Metrowerks CodeWarrior was the original development system for PalmOS and was indeed not free (in either sense). However a bunch of enthusiasts cobbled together some free dev
5.
by jomar 2y ago
Wikipedia says "ISO 8601:2004 established a reference calendar date of 20 May 1875 (the date the Metre Convention was signed), later omitted from ISO 8601-1:2019." I was curious what "reference calendar date" is supposed
6.
by jomar 2y ago
I'm another one who's had two colonoscopies. Try to schedule it for the morning so that most of the fasting time will be while you're asleep. The prep is not a lot of fun, but it's only about half a day and it's ver
7.
by jomar 2y ago
As noted above, what used to be a cool little Wellington-based company got bought by some offshore conglomerate. Lenz himself left about five years ago.
8.
by jomar 3y ago
Probably the older email address is still the primary one for the GitHub account. GitHub took it upon themselves to change email addresses and author names when merging via the UI buttons like "Squash and Merge" in 2018 and then a
9.
by jomar 3y ago
Handy, but is it really easier to type? Or as pleasantly reminiscent of one of the first Unix commands you ever learnt, back in the days when they actually really were multiuser machines? :-)
10.
by jomar 3y ago
That is a nice trick. I've had my main email address in .config/git/config, added an override in ./.git/config for projects that need it, and checked who I am from time to time with [alias] whoami = &q
11.
by jomar 3y ago
Having said that, given that many people do use separate GitHub accounts for their separate private and work personas, and many organisations seemingly expect their employees to do so, perhaps GitHub could consider revising this Terms of Se
12.
by jomar 3y ago
It's always been very clear in their Terms of Service (which obviously everyone reads carefully...): The third bullet point at https://docs.github.com/en/site-policy/github-terms/github-t... -- > One
13.
by jomar 3y ago
Various government departments of those countries use domains under .gouv.fr, .gob.es, .gov.ro respectively. The argument is that fairness and clarity would suggest that the US likewise use .gov.us or some other convention of their choice u
14.
by jomar 3y ago
That was introduced in 1985, almost 40 years ago. For how many decades is this going to be a reasonable argument? In 100 years, will it still be reasonable for the USA to say "we built the thing, so it is appropriate for us to continue
15.
by jomar 4y ago
Export $BASH_SILENCE_DEPRECATION_WARNING as described in the Apple web page pointed to by the nag message, or change your shell to your own version of Bash. See also < https://apple.stackexchange.com/questions/371997&
16.
by jomar 4y ago
Zlib-ng doesn't contain the same code, but it appears that their equivalent inflate() when used with their inflateGetHeader() implementation was affected by a similar problem: https://github.com/zlib-ng/zlib-ng&#x2
17.
by jomar 4y ago
Prior to 1.2.13 released a few days ago, neither of these commits was contained in a zlib release. The CVE exists in the state of the code prior to that first commit, and is fairly obvious when you read the explanation in the commit message
18.
by jomar 4y ago
I too was surprised to see these were shell scripts. I was expecting the grep/fgrep/egrep names to be hard links to the same executable that would check `argv[0]`, as the BSD implementation does. More interesting than the commit d
19.
by jomar 4y ago
Looking at the linked script, it indicates which cow orker to credit. To the OP: You might be able to simplify the script by using `git commit --trailer …`. Or maybe you tried that and it didn't display the message in the editor window
20.
by jomar 4y ago
The scheme proposed in TFA is not particularly amenable to automation: > Can I programatically convert from what I use now? > Unfortunately, probably not Moreover, even if a syntax-aware formatter could detect mistakes made in fol
21.
by jomar 4y ago
This is nice in theory, but it will inevitably get screwed up by your less details-oriented coworkers. The spaces and tabs are mostly invisible, so even if they did care about it these people can't really see the conventions that are i
22.
by jomar 4y ago
TFA is a war story about how infelicities such as caching in tools and “those darn browsers” contributed to the identification of the cause of this issue taking longer than it should have. Once the missing intermediate certificate issue had
23.
by jomar 5y ago
If you want a separate clone you know where to find it, but then you will be plagued by the uncertainty I mentioned in my other comment ( https://news.ycombinator.com/item?id=30400869 ). I did not say that was the only sane w
24.
by jomar 5y ago
If you had two worktrees set to the same branch and made a new commit in one of them (thus changing the commit the branch ref points to), what would happen in the other worktree? Either it wouldn't have the right commit checked out any
25.
by jomar 5y ago
When you're done with a worktree, you just delete it (via `git worktree remove`). Any additional branches or stashes etc are part of the repository that the worktree was part of, and they (of course) remain. When you're done worki
26.
by jomar 5y ago
> For a specific doc fix, a PR is indeed the way to go. If it's not a simple fix, creating an issue on the tracker may also be called for. That is precisely what I did. As noted, there has been no indication (by activity on the is
27.
by jomar 5y ago
I agree with everything you say, and alluded to much of it in the parent post. I myself also volunteer happily on a number of projects, and attempt to keep up with similar deluges on those projects. For someone like myself who is not alread
28.
by jomar 5y ago
For a one-character typo, I would probably have just reported it as an issue. An issue is sufficient to say what fix is needed, and in some ways it's easier for a maintainer to make such a fix themselves than to verify a change made by
29.
by jomar 5y ago
A small Perl script < https://github.com/jmarshall/manconvert > that grinds a subset of man page nroff syntax directly into HTML. (That subset being “the constructs that are used in the man pages that it's use
30.
by jomar 5y ago
Dude, you seem to be very keen to put words into other people's mouths. Perhaps you should reflect upon that.

More ›