chrishill89

12 ms·

1. 31.▲
   by chrishill89 11mo ago

   > Might as well squash as nobody wants to deal with untested in-between crap. I would rather deal with nice and tidy but untested commits rather than a very well-tested but too monolithic squash. If you test the eventual merge then you
2. 32.▲
   by chrishill89 11mo ago

   The question as stated answers itself. Some are able to make nice multi-commit PRs. So they do.
3. 33.▲
   by chrishill89 11mo ago

   I found a bug in a OSS program where an entry contained a gibberish string. This was C so apparently it was some not-properly initialized variable. I couldn’t hope to trace down where that occurred. But with time to write a bisect script an
4. 34.▲
   Note that ambiguous commit IDs are not even remotely as scary (2024)(lore.kernel.org)

   1 points by chrishill89 1y ago|0 comments
5. 35.▲
   by chrishill89 1y ago

   > You can always use git notes for yourself but it is as I called it gimmick feature. I can make a bet you will use it for a week maybe couple weeks and then just stop because in description it sounds good but in practice - no one is usi
6. 36.▲
   by chrishill89 1y ago

   There’s plenty of data which is extra-commit (doesn’t belong in the commit messages but is relevant). Like if the tests passed[1], manual testing notes, iteration on code review, notes for code spelunking when you find a problematic 6+ mon
7. 37.▲
   by chrishill89 1y ago

   There are many uses for Git notes even though you might use a project management tool. Particularly all those things which are relevant for developers only, or that the developers can use as the data source for "higher-level" goal
8. 38.▲
   by chrishill89 1y ago

   By default no copying will be done. While `notes.rewrite.amend` and `notes.rewrite.rebase` are true you also need `notes.rewriteRef` which tells it what notes refs should be rewritten. And it has no value by default. (you can set it to a gl
9. 39.▲
   by chrishill89 1y ago

   "Pickaxe" most often means those options. But it's also a (apparently legacy) command alias for git-blame.
10. 40.▲
    by chrishill89 1y ago

    I use Git Notes all the time. It doesn’t look like the article mentions that you can attach the notes to emails you send out with git-format-patch(1) and git-send-email(1). I use them for emails to attach comments on patches that shouldn’
11. 41.▲
    by chrishill89 1y ago

    I create issues for myself. I sometimes create branches with informal issue keys like `<three letters>-<incrementing number>`. I use `git bug webui` to type edit issues. That’s it. All I would like as a nice-to-have is support f
12. 42.▲
    by chrishill89 1y ago

    Thanks. I can’t push it to the issue tracker since they don’t have one. Bug reports go to the mailing list.
13. 43.▲
    by chrishill89 1y ago

    I use this to note potential issues in my copy of the Git project. For outright bugs though I report them to the project.
14. 44.▲
    by chrishill89 1y ago

    I’ve just used it two times in the last few months. One was to track down a commit which triggered a bug I found in Git. I wouldn’t be able to troubleshoot it myself. And I couldn’t send the whole repository because it’s not OSS. But with a
15. 45.▲
    by chrishill89 1y ago

    Here’s the most relevant (to me) difference: - The real unit of change lives in Git - The real unit of change lives on some forge I want it to live in Git.
16. 46.▲
    by chrishill89 2y ago

    This is an active fork: https://github.com/dathere/qsv
17. 47.▲
    by chrishill89 2y ago

    The Git project has a script for that: https://github.com/git/git/blob/master/contrib/contacts/git-...
18. 48.▲
    by chrishill89 2y ago

    > "They're just another kind of value" and "Just crash and restart" are both wrong, error handling is much more complex than that. Regarding the first slogan: it is correct that they are just another kind of valu
19. 49.▲
    by chrishill89 2y ago

    What a great resource. I’ve been in the errors-as-values (like Rust and Haskell) camp for over a decade. But I think you need to go a bit beyond that philosophy (i.e. not just as a slogan) in order to truly unlock what treating errors as v
20. 50.▲
    by chrishill89 2y ago

    I know. I don’t understand why the Linux Kernel uses a hard-coded abbreviation instead of just letting Git figure out how long it should be (edited my comment now).
21. 51.▲
    by chrishill89 2y ago

    > Presumably the problem is that these tools only take the abbreviated hash into account. Not also the subject: Well the first mentioned script: > > Tools like linux-next's “Fixes tag checker”, has `get_full_hash`[1] which use
22. 52.▲
    by chrishill89 2y ago

    Presumably the problem is that these tools only take the abbreviated hash into account. Not also the subject: <abbrev. hash> ("<subject>") You also have another data point. You only need to search in the his
23. 53.▲
    by chrishill89 2y ago

    You want to rewrite each commit snapshot in isolation? Like fix the formatting for each? Sounds like `git test fix` from git-branchless. https://blog.waleedkhan.name/formatting-a-commit-stack/
24. 54.▲
    by chrishill89 2y ago

    > Or maybe we need something more than plaintext to store code and the meta data around it before we can get to this point. I'm sure it has been already done multiple times in different ecosystems but there must be a way to standard
25. 55.▲
    by chrishill89 2y ago

    Thanks. Yeah, I've also been having similar thoughts for logging systems. In particular right now we (at my job) configure the log level through compile-time switches. It would be nicer to be able to toggle things dynamically. Yes,
26. 56.▲
    by chrishill89 2y ago

    I agree with the others here that classic assert statements are in a weird spot. You enable it when testing, in other words when the data flowing through your program is likely to be constrained and lazy. And then turn it off when your prog
27. 57.▲
    by chrishill89 2y ago

    > For machine-readable formats, I'd argue length-before-text is simpler to parse than splitting by separators Yes. > even before having to add extra application logic to handle this method being fallible (e.g: if you want to use
28. 58.▲
    by chrishill89 2y ago

    Then I don't understand. Like the sibling comment said the really "problematic" character in TSV is the line feed. But a tab can occur as well. The format that I described does not already exist in the form of TSV. And fur
29. 59.▲
    by chrishill89 2y ago

    Thanks for that. Handy. I think I’ll have use for that myself.
30. 60.▲
    by chrishill89 2y ago

    Whoops, meant to link to qsv https://github.com/jqnatividad/qsv