(hidden) qbhpV9DHv

words:	0 + 242 = 242
last update:

Linked Mentions (10 in 9 pages)

January 7th, 2022 (1)
- [[(hidden) GSgm9FsKi]] you can use [[(hidden) qbhpV9DHv]] for this too! `Git.Reference`
March 21st, 2022 (1)
- {{[[TODO]]}} the `zdiff3` problem with [[(hidden) qbhpV9DHv]]
March 24th, 2022 (1)
- {{[[TODO]]}} usage w/ #[[(hidden) gpwvvVB_X]] is annoying because the expected node version that #[[(hidden) qbhpV9DHv]] was built for might differ
March 27th, 2022 (1)
- [[(hidden) qbhpV9DHv]] outdated build...
March 30th, 2022 (2)
- heh, looks like [[(hidden) qbhpV9DHv]] is the best we can do (unless we fork git & implement the core functionality in [[(hidden) U5k5oJ6YK]] kek)
- re: [[git]] bindings, [[(hidden) qbhpV9DHv]]
April 2nd, 2022 (1)
- checking [[(hidden) qbhpV9DHv]]'s ([[(hidden) AuQNzoeTk]]) changelog
  - https://github.com/nodegit/nodegit/blob/master/CHANGELOG.md
  - wow we've been using a version from 2019. all the newer ones are pre-releases. will try out `@next` soon, gotta read thru further
  - `commit-graph`?
    - https://github.com/libgit2/libgit2/pull/5764
      - https://github.com/libgit2/libgit2/issues/5757
      - https://github.blog/2018-09-10-highlights-from-git-2-19/#[[(hidden) e1uk5UrBJ]]er-content-commit-graphs
        
        [[git]] `range-diff`? 👀
        
        https://github.com/git/git/commit/348ae56cb2266d3294611112ae0368386124d720
        
        {{[[TODO]]}} #read [[git]]'s `command-list.txt`
        
        {{[[TODO]]}} maybe `update-ref` instead of branch `reset --hard`
        
        meh
        
        {{[[DONE]]}} #read `man gitrepository-layout`
        
        {{[[TODO]]}} #read `user-manual`
        
        https://git-scm.com/docs/user-manual.html
        
        ooo they even have some similar ideas to [[git-stacked-rebase]] -- "Creating the perfect patch series"
        
        https://git-scm.com/docs/user-manual.html#[[(hidden) G97ohL3l8]]patch-series
July 28th, 2022 (1)
- first thought of making use of [[(hidden) x7o01uO13]], but idk if it's easier to parse thru it everytime & decode (using e.g. [[(hidden) qbhpV9DHv]]) if a reference is a branch or not
  - instead maybe could use a post-checkout hook (if there is one) (if isn't, could contribute w/ example use case), and simply writing out the branch name that was checked out (& any other metadata)
    - pretty similar to reflog, tho u get to take metadata __at the time that you perform the checkout__, which could prove more useful instead of trying to infer from the reflog
December 13th, 2022 (1)
- (hidden) JNd45oumO [[(hidden) Ke7lXiNQh]] [[(hidden) qbhpV9DHv]]
April 22nd, 2023 (1)
- {{[[TODO]]}} need to get rid of [[(hidden) qbhpV9DHv]]... [[(hidden) leKN0KvQS]]