Viewing profile — jomar
jomar
HN member- Joined
- Tue, Dec 20, 2011, 2:52 AM UTC
- HN karma
- 224
- Public activity
- 73 items
- HN profile
- View on Hacker News ↗
About jomar
No profile information was provided.
Recent public activity
-
comment
Comment #47943947
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 chang…
-
comment
Comment #47683425
Apparently it's about as expected for a southern giant pouched rat. But he was indeed a particularly good one!
-
comment
Comment #47175077
> 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…
-
comment
Comment #43074725
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 wh…
-
comment
Comment #43042902
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…
-
comment
Comment #42364567
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.
-
comment
Comment #37908324
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 …
-
comment
Comment #37906493
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 ma…
-
comment
Comment #37905875
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 wit…
-
comment
Comment #37905759
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…
-
comment
Comment #37905611
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/g…
-
comment
Comment #36844548
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 lik…
-
comment
Comment #36840832
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 b…
-
comment
Comment #33355324
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.…
-
comment
Comment #33215366
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: http…
-
comment
Comment #33215295
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…
-
comment
Comment #33192019
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 imple…
-
comment
Comment #32468621
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…
-
comment
Comment #31482034
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…
-
comment
Comment #31480739
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 t…
-
comment
Comment #31433144
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 shou…
-
comment
Comment #30404563
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=30400…
-
comment
Comment #30401052
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? E…
-
comment
Comment #30400869
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, a…
-
comment
Comment #29839021
> 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, t…