From: "Carlsson, Magnus" <Magnus.Carlsson@arris.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Fetching commit instead of ref
Date: Mon, 18 Dec 2017 12:30:23 +0000 [thread overview]
Message-ID: <1513600223353.28799@arris.com> (raw)
Hi
I am involved in the git-subrepo project (https://github.com/ingydotnet/git-subrepo/). It's an attempt to simplify the inclusion of repos into other repos.
In a certain situation I would really need to fetch all commits related to a specific commit (SHA). I have read the git fetch documentation and found nothing regarding this. It only seems to support fetching references.
I found some traces on stack overflow:
https://stackoverflow.com/questions/14872486/retrieve-specific-commit-from-a-remote-git-repository
Following that recommendation it feels like it almost works:
$ git fetch subrepo 50f730db793e0733b159326c5a3e78fd48cedfec:refs/remote/subrepo/foo-commit
remote: Counting objects: 2311, done.
remote: Total 2311 (delta 0), reused 0 (delta 0), pack-reused 2311
Receiving objects: 100% (2311/2311), 703.64 KiB | 0 bytes/s, done.
Resolving deltas: 100% (1174/1174), done.
----> So far so good, but then an error message appear:
error: Server does not allow request for unadvertised object 50f730db793e0733b159326c5a3e78fd48cedfec
----> And nothing seems to be fetched.
Is there a way to fetch a commit and any ancestors to that commit based on a SHA?
Why do I need this?
In git-subrepo we try to recreate another repo within our main repo. Creating the necessary parent references when they appear. In some cases we need to make sure that we have access to the correct commits from the subrepo, but we don't have any references except a SHA.
-- Magnus
MAGNUS CARLSSON
Staff Software Engineer
ARRIS
o: +46 13 36 75 92
e: magnus.carlsson@arris.com
w: www.arris.com
ARRIS: Legal entity: Arris Sweden AB - Registered Office: Teknikringen 2, 583 30 Linkoping, Sweden - Reg No:556518-5831 - VAT No:SE 556518-583
This electronic transmission (and any attached document) is for the sole use of the individual or entity to whom it is addressed. It is confidential and may be attorney-client privileged. In any event the Sender reserves, to the fullest extent, any "legal advice privilege". Any further distribution or copying of this message is strictly prohibited. If you received this message in error, please notify the Sender immediately and destroy the attached message (and all attached documents).
next reply other threads:[~2017-12-18 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 12:30 Carlsson, Magnus [this message]
2017-12-18 18:16 ` Fetching commit instead of ref Jonathan Tan
2017-12-18 18:22 ` Stefan Beller
2017-12-18 18:44 ` Junio C Hamano
2017-12-19 8:41 ` Carlsson, Magnus
2017-12-19 16:07 ` Junio C Hamano
2017-12-20 7:48 ` Carlsson, Magnus
2017-12-22 18:47 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1513600223353.28799@arris.com \
--to=magnus.carlsson@arris.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).