Sebastian Thiel

A good example for its use is a [freshly parsed commit](https://docs.rs/git-object/0.12.2/git_object/immutable/commit/struct.Commit.html) whose memory is backed by a buffer somewhere else. The goal is to make clear that these fields represent...

Thanks so much! Part of me was afraid I'd be told it's all wrong as it was so strongly discouraged 😅. Also thanks for the prioritization, even though I think...

Since there hasn't been a lot of movement in the past 9 months and since `bstr` is a very, very important dependency for `gitoxide` and probably countless other crates, I...

> For what it's worth, it would have probably been an order of magnitude more work to onboard someone else to do the 1.0 release than to just do it...

I think helpful to address would be issues that could potentially lead to breaking changes before 1.0. Not truly understanding if this is the case or not with what I...

> @Byron I think these are the related issues for that, right? https://github.com/BurntSushi/bstr/issues/84 and https://github.com/BurntSushi/bstr/issues/86. I specifically skipped over those because I do not believe there are any breaking changes...

> How do you feel about Rust 1.60 as the MSRV? I'd be OK with it, thanks for asking.

bcmd can now handle chained subcommands automatically, which will greatly improve usability and 'remixability'. 'be' command framework is implemented, was astonishingly simple. After all, it's just a command whose characteristics...

Still TODO: per sub-command settings. It's trivially done. Think about making this a general facility, that is used used by the 'be' command framework.

I would clearly prefer markdown over rst, as it is easier and quite en-vogue, which nice tools alongside of it. It seems that mkdocs can't include documents. This is in...