From: "Stanisław Drozd" <drozdziak1@gmail.com>
To: git@vger.kernel.org
Subject: How do smart git helpers transport objects?
Date: Sat, 13 Oct 2018 10:08:17 +0200 [thread overview]
Message-ID: <79cad128-383f-9a9a-cb53-6089afa36081@gmail.com> (raw)
In-Reply-To: <100fc0a7-a7fd-e6ba-937e-f795b30b3f35@gmail.com>
Hello,
I'm writing a remote helper and decided implement the `fetch` and `push` capabilities,
but one thing still remains a mystery for me. Namely, is my helper supposed
to instantiate and pin git objects in `GIT_DIR` upon `fetch <sha> <ref>`?
In general I'm trying to determine how exactly I need to proceed upon receiving
this command and find out whether libgit2 will be able to help me with whatever that is.
I'm also contemplating hooking up to libgit2's transport API, but IIUC its operation isn't
very well suited for the backend I'm trying to use behind the scenes (IPFS,https://ipfs.io/,
long story short it's P2P and doesn't have a "server side" per se).
Thanks,
Stan
PS: If my libgit2 questions feel outside scope I'd gladly join a community more focused
on libgit2; I'm already on #libgit2 on freenode, but there's only 11 people there ATM
parent reply other threads:[~2018-10-13 8:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <100fc0a7-a7fd-e6ba-937e-f795b30b3f35@gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=79cad128-383f-9a9a-cb53-6089afa36081@gmail.com \
--to=drozdziak1@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).