libgit2 VS GitJournal

Everything that is replicated on the network is stored as a Git object, using the libgit2[0] library. This library uses hardened SHA-1 internally, which is called sha1dc (for "detect collision").

[0]: https://github.com/libgit2/libgit2/blob/ac0f2245510f6c75db1b...

This is delightful and I can't wait to try it out. Right now, the libgit2 project (https://github.com/libgit2/libgit2) has a custom HTTP git server wrapper that will throttle the responses down to a very slow rate. It's fun watching a `git clone` running over 2400 baud modem speeds, but it's actually been incredibly helpful for testing timeouts, odd buffering problems, and other things that crop up in weird network environments.

I'd love to jettison our hacky custom code and use something off-the-shelf instead.

I've built a UI on top of libgit2 and I wish that this blog post expanded on which new features are missing (sparse checkout?).

To quote: "The migration to Git Executable will allow us to resolve long-standing issues with GitKraken Client, such as poor LFS performance, SSH configuration support and many other features/performance improvements."

I agree on LFS performance on Windows. SSH config support is a pain due to libssh2 but openssh support is on the way (https://github.com/libgit2/libgit2/pull/6617).

There are many cons to using the Git executable itself (parsing output, error reporting, version handling). Seems to me that there's more to this?

I'm curious about the license change? This is an executable is it not? Invoking it as a separate process does not require you make the software calling it GPL so switching to MIT should have no affect in the common case.

If the authors really wanted a more permissive license, then instead of relicensing from AGPL to MIT they should have gone AGPL with linking exception. An example of a project that does this is libgit2 [1]. This licensing is more permissive but still permits the author to sell commercial licenses to those making closed-source code changes.

[1] https://github.com/libgit2/libgit2#license

Using libxlsxwriter and libgit, it's straightforward -- just putting the equivalent of git shortlog and lines added and removed into a line of cells.

It crossed my mind to do a daily Jupyter notebook but I typically don’t need them to be interactive code. The closest solution that I’ve found looks like: GitJournal does anyone have experience with this or other solutions?

GitJournal comes to mind, "Mobile first Markdown Notes integrated with Git".

https://github.com/GitJournal/GitJournal

Recent HN discussion: https://news.ycombinator.com/item?id=31914003

See this gem too - https://gitjournal.io/

If you are working with text files and git, gitjournal works well for me. It defaults to Markdown, but if you just edit in raw mode, you can do anything in the text file.

I've been searching for a while for something that would let me simply publish from my phone. I actually saw GitJournal in the Play store a couple of times, but I assumed it would only use GitHub to back up its own proprietary file format and so be useful.

There are plenty of desktop/mobile apps for working with markdown. (I've been using Notable (desktop) and GitJournal (mobile ) for an Evernote-like experience.) And markdown is often extended with support for internal links like a wiki, attachments, diagramming (see Mermaid), and easy export to other formats like HTML.

GitJournal: Mobile first Markdown notes synchronized with Git\ (108 comments)