Viewing profile — peff
peff
HN member- Joined
- Mon, Oct 22, 2012, 7:21 AM UTC
- HN karma
- 655
- Public activity
- 80 items
- HN profile
- View on Hacker News ↗
About peff
No profile information was provided.
Recent public activity
-
comment
Comment #49019714
If it's used for both, then you couldn't have "--" itself as a pathspec. In your first example, the current meaning is: a pathspec containing "rev", "--", and "pathspec".
-
comment
Comment #37892511
This is the one I remember seeing as a kid: https://www.reddit.com/r/comicbookcollecting/comments/15vvfj...
-
comment
Comment #34339839
On the page you linked, you can see that `ctype.h` reserves all prefixes of `is[a-z]` and `to[a-z]`, and `string.h` reserves `str[a-z]`. These come from the C standard (in C99, it'…
-
comment
Comment #27181250
What do you want `blame --porcelain` to do that it doesn't? Using: git blame --line-porcelain "$1" -L "$2,"$2" | perl -MPOSIX=strftime -lne '/^author-time (\d+)/ and print strftime…
-
comment
Comment #24229103
Sounds neat, but I think your name runs afoul of Git's trademark; see https://git-scm.com/trademark
-
comment
Comment #22891446
No, it's not the root cause, though it did exacerbate it. See the comment in https://news.ycombinator.com/item?id=22890633 .
-
comment
Comment #22890633
The parser problem made it worse, but it was neither necessary nor sufficient for the vulnerability. We are fixing it, but decided to leave it out of the critical release path. See…
-
comment
Comment #22890616
That was discussed before the fix, but it doesn't matter. The helper protocol specifies a raw newline as the delimiter, and both sides of the conversation parse on that.
-
comment
Comment #20802408
The commit messages that add them to banned.h discuss alternatives, though most of the explanations are Git-specific and assume you'll look elsewhere to figure out how to actually …
-
comment
Comment #20794333
Yes, you're right. Patches welcome. We do our development on a mailing list; see https://git-scm.com/docs/SubmittingPatches for details. However, if you're more comfortable using G…
-
comment
Comment #20794312
I see a lot of comments to the effect of "shouldn't XYZ also be banned". The answer is that we're not necessarily trying to be exhaustive. The point is to flag common errors before…
-
comment
Comment #18477327
> the .git/index file, which uses mmap, is synced incorrectly by file sync tools relying on mtime This part implies that the index file is written via mmap, but that's not true. It…
-
comment
Comment #18294849
Perl has shipped with a `rename` utility for ages, that you can use like: rename 's/foo/bar/' *.ext Of course you have to know Perl...
-
comment
Comment #18061209
This makes sense for some completions (e.g., vanilla lists of options). But often the completion depends on other context that the binary doesn't need to know about. For example, I…
-
comment
Comment #17784162
I'm not sure how I feel about sticking so much complexity into the kernel, but one thing I would really enjoy is being able to use standard tools like `strace` on TLS-speaking proc…
-
comment
Comment #17228179
I'm a GitHub employee and spend most of my time contributing to the Git project. I've always been very happy about how GitHub supported my participation in the community. Sometimes…
-
comment
Comment #17182846
No problem! Thanks for all your work on this. I should have clarified above, too: there were folks from GitHub, Microsoft, and Google working on the various fixes.
-
comment
Comment #17182764
A few important points that aren't mentioned in the post: - you have to tell git to use submodules for this to trigger (so `clone --recurse-submodules` or a manual `git submodule u…
-
comment
Comment #16823341
Try the diff-highlight script which can be found at: https://github.com/git/git/tree/master/contrib/diff-highligh...
-
comment
Comment #16777323
Er, sorry, I meant to say "...the new features in Git v2.17". I think that keeps it clear but without making it overtly look like a release announcement.
-
comment
Comment #16773923
Try "Git 2.9 is out!": https://blog.bitbucket.org/2016/06/13/git-2-9/
-
comment
Comment #16773889
Thanks for the feedback in this thread (I'm the author). The main goal _is_ to let people know about the new version, and about new features they can use (there are a ton of other …
- story
-
comment
Comment #16677674
You should probably avoid `--color`, as it turns on color unconditionally, even if output is going to a file. In older versions of Git the %C color placeholders were unconditional …
-
comment
Comment #16677666
I think they meant to say "might do --decorate by default" (which Git does since v2.13.0).