bicolao

11 ms·

61.
by bicolao 7y ago
It exposes bugs in your make rules.
62.
by bicolao 7y ago
> What could possibly go wrong? ;) It's not a bug, it's a feature. This adds.. ehem.. a new dimension to integer numbers (or even complex numbers, we'll call them supercomplex numbers).
63.
by bicolao 7y ago
> This will tell you "Firefox process 4567 is talking a lot ycombinator.com" and you'll know whether 4567 is also one of the chattiest talkers right now. But that's what nethogs does.
64.
by bicolao 7y ago
So close, only three more bytes and we have a 42-byte file that prints 42.
65.
by bicolao 7y ago
> You know that it literally means 'Noodles From Vietnam' It's short for (Mi) (Vi)et (Na)m, which is basically Vietnamese Noodles. You can already guess "Mi" is noodles in Vietnamese.
66.
by bicolao 7y ago
Vietnamese does not really belong in CJK group because it's written with Latin alphabet.
67.
by bicolao 7y ago
It's just a small step to generate machine code, this fork [1] can generate an executable, or run it JIT style, both on x86 (there's also the 'arm' branch) [1] https://gitlab.com/pclouds/c4
68.
by bicolao 7y ago
Yeah some of those ways are known and there may be a way to recover those lost changes. It's still too early to see if something will materialize.
69.
by bicolao 7y ago
> When you hoping to have git restore in the official git release? If things go well, maybe v2.23.0, unless we find serious UX flaws and scrape the whole thing.
70.
by bicolao 7y ago
> I would like an option to make the index go away By Git design, you will have to face the index when you have merge conflicts. I don't know how to avoid that (and now is not the time for fundamentally change how conflict resolutio
71.
by bicolao 7y ago
"git restore file" does reset worktree. Sorry I didn't mention it. If neither --worktree or --staged is present, the default target is the worktree. It still restores worktree from the index though. But if your workflow ignor
72.
by bicolao 7y ago
Since this is posted on Git mailing list, the reply is here https://public-inbox.org/git/20190515103031.GA29149@ash/
73.
by bicolao 7y ago
"git restore --staged" should be the same as "git reset -- file" (--mixed, --soft and --hard cannot be used with individual files). "git restore --worktree" is the same as "git checkout -- file". &quo
74.
by bicolao 7y ago
In a near future, hopefully we will have two new commands, git-switch and git-restore. The former is only about switching branches, the latter restoring files. Then you can stay away from the overloaded git-checkout. See https://
75.
by bicolao 7y ago
This particular pattern should be fixed in a future git (hopefully). There's a new command that supports all these git restore --staged file # reset the index from HEAD git restore --worktree file # reset the worktree from the index
76.
by bicolao 8y ago
This seems to be about statically typed languages like Haskell. Can it be used (and be useful) for dynamically typed languages like Scheme?
77.
by bicolao 8y ago
It's a bug that "git checkout" does not complain in this case. I'll try to fix or report it.
78.
by bicolao 10y ago
> I don't like the living-on-the-edge-attitude that Linus and others here promote regarding Sha1 in git. First, attacks only get faster over time. What costs millions today is likely to be achievable on commodity hardware in the com
79.
by bicolao 10y ago
Gauche Scheme also has something called CiSE (C in S-Expressions) [1]. It's a bit under-documented though, but you can see examples throughout Gauche Scheme source code, for example [2] [1] https://github.com/shirok&#x2
80.
by bicolao 10y ago
Do partial commits. Run a new interactive rebase session, set "edit" to all those commits so you can test out individual ones and fix up some more if needed. Basically the same outcome, but less manual diff editing.
81.
by bicolao 10y ago
This is from 2015, not sure if it's that old. https://github.com/tomga/genode/commit/c8a64b5c3465cde1723b2...
82.
by bicolao 11y ago
> It would be a pity if an ignorant user copied a repository to another filesystem only to find out that certain operations suddenly break. Once tested (or enabled without testing if you know what you're doing), the location of the
83.
by bicolao 11y ago
Because it relies on filesystem changing directory's mtime every time a file/dir is added or deleted in that directory. Not every filesystem supports that.
84.
by bicolao 11y ago
US west side on http://map.norsecorp.com/ looks like fireworks. I wonder if that where Github servers are
85.
by bicolao 11y ago
The question is how he hands his draft to his editor. Floppy disks still exist?
86.
by bicolao 11y ago
>> How do I stop Linux from doing this? > You can't disable disk caching While that's true, you can temporarily stop (1) the cache it with "echo 3 >/proc/sys/vm/drop_caches" and enjoy a sh
87.
by bicolao 11y ago
part of the --untracked-cache feature is to reduce the cost of applying .gitignore patterns. When you have tons of files to check against some patterns, even strcmp() accumulates up.
88.
by bicolao 11y ago
Once I was handling a big data set for natural language processing. It's big enough it nearly ate all my memory and was somewhat slow if I remember correctly. Then I switched to a C-based toolkit, memory usage dropped significantly. I
89.
by bicolao 11y ago
> One of the best ways to discover hidden implementation issues or oversights in a spec or existing documentation... There are issues. And there is the legendary "pack v4" (current pack versions are 2 or 3) but it still a work
90.
by bicolao 11y ago
https://github.com/git/git/blob/master/Documentation/technic... More detail than that would require reading the source code..

More ›