public inbox for nncp-devel@lists.cypherpunks.ru
Atom feed
From: Sergey Matveev <stargrave@stargrave•org>
To: nncp-devel@lists.cypherpunks.ru
Subject: Re: Announcing gitsync-nncp
Date: Fri, 20 Aug 2021 13:41:31 +0300 [thread overview]
Message-ID: <YR+G3DmkqCLZUosR@stargrave.org> (raw)
In-Reply-To: <87fsv6hgoh.fsf@complete.org>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
Greetings!
*** John Goerzen [2021-08-18 11:16]:
>https://github.com/jgoerzen/gitsync-nncp
Impressive! My appreciation!
Just out of curiosity, possibly I read badly and too quickly, possibly I
am not taking in account something, or forget how git works, but: each
remote gitsync-accessible repository is "identified" only by a single
branch in your scheme. Can remote/branch be used instead of a single
branch? Instead of "gitsync-nncp/bob" branch, can there be used
"gitsync-bob" git-remote with possibly several branches in it instead
(and dummy send/fetch URLs)? Git-remote can be considered as a some kind
of a namespace/aggregation of branches (plus some URLs/rules where to
push/fetch it) in my opinion. Or using "git remotes" abstraction brings
more problems and complications? But you won't be limited to the single branch.
--
Sergey Matveev (http://www.stargrave.org/)
OpenPGP: CF60 E89A 5923 1E76 E263 6422 AE1A 8109 E498 57EF
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-08-20 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 16:16 Announcing gitsync-nncp John Goerzen
2021-08-18 19:49 ` Jonathan Lane
2021-08-18 20:19 ` John Goerzen
2021-08-20 10:41 ` Sergey Matveev [this message]
2021-08-20 12:53 ` John Goerzen