One of the reasons we've decided to use Ngit as our CLI is to ensure interoperability dynamically, rather than through written specs. This means that if we need some new CLI feature, we'll be making a ngit proposal.
I've been testing the CLI for months now, and have had no problems working together with Dan, so we want to use his stuff and maintain the collaboration.
He's very responsive and hard-working, and his own ngit and gitworkshop repos are listed on the first page.
Laeserin
npub1m4n…c2jl
2024-06-30 07:54:44
in reply to nevent1q…e8wk
Author Public Key
npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jlSeen on
wss://relay.noswhere.comPublished at
2024-06-30 07:54:44Event JSON
{
"id": "a66a88573e7a8c81950ac6c08e3c57d700e04c391c3fb761da0a55cc2170abe8",
"pubkey": "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319",
"created_at": 1719726884,
"kind": 1,
"tags": [
[
"e",
"5468e9c35ce30daf1f06a6bc7e166b94bcd27660ad1c1b73803705feef36d32b",
"",
"root"
],
[
"e",
"c9947d443787dd9cbac387ddd86542f43acd48eee586db39eb660c95913a400b",
"",
"reply"
]
],
"content": "One of the reasons we've decided to use Ngit as our CLI is to ensure interoperability dynamically, rather than through written specs. This means that if we need some new CLI feature, we'll be making a ngit proposal.\n\nI've been testing the CLI for months now, and have had no problems working together with Dan, so we want to use his stuff and maintain the collaboration.\nHe's very responsive and hard-working, and his own ngit and gitworkshop repos are listed on the first page.",
"sig": "e25d89b233fac9da8e70577770b314831cc6b6c963e0d41cf16e644a3db09be5fda29e47a8dcd7070876a7dbdf9762e61c5a08dc1b124b4ed83f16bbcc7a9879"
}