Viewing profile — avgcorrection
avgcorrection
HN member- Joined
- Mon, Sep 27, 2021, 4:39 PM UTC
- HN karma
- 4,323
- Public activity
- 2,979 items
- HN profile
- View on Hacker News ↗
About avgcorrection
No profile information was provided.
Recent public activity
-
comment
Comment #39629576
I’ll try to do better in the next life.
-
comment
Comment #39622855
> But go ahead and use the FFI and things aren't so rosy. Usually the GC can cooperate with allocated memory from the other side of the FFI, but this requires care and attention to…
-
comment
Comment #39621477
What was difficult about what I wrote?
-
comment
Comment #39620718
> Back to TCP. Earlier for the sake of simplicity I told a little fib, and some of you have steam coming out of your ears by now because this fib is driving you crazy. I said that …
-
comment
Comment #39618517
Ok. That could work if you found a group of people who are interested in such an all-in-one package. Gitlab is apparently working on a sort of cross-forge protocol (probably motiva…
-
comment
Comment #39617728
Amendment: I just found out that I do have at least one use for git-stash, which is when I am stuck in the middle of a rebase somewhere and made an edit intended for another point …
-
comment
Comment #39610553
And Fossil is an entirely different VCS. What’s the alternative? That at least N projects cooperate and agree on a common design before they do the implementation? (Then maybe some…
-
comment
Comment #39606629
My comment was totally unclear. By primitive I mean that it scales from very primitive operations (just snapshot) to supporting high-level workflows (refactoring, testing, verifyin…
-
comment
Comment #39606547
IMO you don’t need anything more than commits. The by-hand is writing WIP in the commit message. If that is an inconvenience then I’ll make a commit alias. The index + commits is f…
-
comment
Comment #39606525
I think that you (like me) prefer to use commits in places where many others prefer to stash. Personally I think the stash command is too primitive to bother with for all things ex…
-
comment
Comment #39597616
https://news.ycombinator.com/item?id=39357068 The submitter unhelpfully didn’t mention the name in the title.
-
comment
Comment #39597514
You don’t have to interpret it as you-always-do-this. Just sometimes you want a worktree (or clone): maybe the bug fix needs to be applied to an old, old release which would invali…
-
comment
Comment #39597497
“Not in a position to commit” in Git makes as much sense as “not in a position to save the file” (in your editor) in 2024. Git is in a sense a primitive tool: only about snapshotti…
-
comment
Comment #39597451
This is the way. Just commit. You can undo it later or whatever, but at least it’s there. Just one concept instead of (1) commits (2) stash (3) oh these changes, eh, I don’t know w…
-
comment
Comment #39597233
> The thing that annoys me about worktrees is that you can't have two checked out to the same commit at the same time Checking out the same commit is fine. You just can’t checkout …
-
comment
Comment #39597091
The first big thread on GitButler (recent) left me scratching my head. All the material with jargon like “virtual branches” just left me confused. It was like jumping into a how-to…
-
comment
Comment #39594440
Maybe there could be some utility for a decently general Graph type that can be used for high-level testing and verification. Maybe you could implement your efficient graph per-pro…
-
comment
Comment #39580369
The private key that I would hypothetically sign commits with? Then signing commits is compromised too. I’m not sure what point you’re making. On the other hand if I don’t sign my …
-
comment
Comment #39580264
It doesn’t seem hard to attribute 1/5 commit in a PR to another person. Then you publish it, no one checks out the individual commits (because that’s how forges are like in my expe…
-
comment
Comment #39580225
Why are you afraid of identity theft in this context?
-
comment
Comment #39580222
I am also able to pee in my office mate’s coffee cup. What should we do to mitigate that threat model?
-
comment
Comment #39580218
Completely correct that you should have a reason for signing something which goes beyond the vacuous “why not”. In my own work, the surrounding context is sufficient verification. …
- comment
-
comment
Comment #39567015
Report it.
-
comment
Comment #39566820
You struggle to imagine a programmer passing a value of the wrong type to a function?