git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alejandro Aguila <aguilasainz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Cloning an specific commit from the hash
Date: Thu, 03 Aug 2017 10:28:49 -0700	[thread overview]
Message-ID: <xmqqtw1opnla.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CA+kp=uoHiP8t_40yZvT7r9ziB4uSxgcc=NRY0+XzQJDkuJpx4A@mail.gmail.com> (Alejandro Aguila's message of "Thu, 3 Aug 2017 11:27:05 -0500")

Alejandro Aguila <aguilasainz@gmail.com> writes:

> I've been working with Oscomo's project OpenBSC
> https://github.com/osmocom/openbsc and my old hardware won't work with
> the latest version, which is 0.15. So I asked for help to osmocom guys
> and there's someone who told me that his version is working with the
> same hardware I have, so have gave me the OpenBSC hash for it (
> 7f100c9712de5c684462e809bf31a58c0c326337 ).
>
> To be honest I don't use git more apart of cloning repos, so I would
> like to know how can I pull the files for that hash. And since OpenBSC
> has some dependencies that are in osmocom's github repo, I don't know
> if I can get the version that worked for the one committed in the
> hash.

When a user of a project that uses Git says "try this version"
without telling you on which branch that version appears, that
statement typically means that anybody who clones that project
would get the commit, i.e.

    $ git clone https://github.com/.../openbsc
    $ cd openbsc
    $ git checkout 7f100c9712de

This will give you a checkout without being on any named branch,
which would be sufficient for you to build; if you want further work
on top of that commit, you might want to do the last step more like
so:

    $ git checkout -b mybranch 7f100c9712de

If you are not developing at all, then starting at this URL

https://github.com/osmocom/openbsc/commit/7f100c9712de5c684462e809bf31a58c0c326337

and clicking around, you should be able to find this URL

https://github.com/osmocom/openbsc/archive/7f100c9712de5c684462e809bf31a58c0c326337.zip

which would presumably give you a Zip archive that contains the
files in that particular commit.



  reply	other threads:[~2017-08-03 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 16:27 Cloning an specific commit from the hash Alejandro Aguila
2017-08-03 17:28 ` Junio C Hamano [this message]
2017-08-03 17:55   ` Alejandro Aguila
2017-08-03 20: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=xmqqtw1opnla.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=aguilasainz@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.
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).