From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: bruce <badouglas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: contents of a .git file
Date: Mon, 18 May 2020 01:01:31 +0000 [thread overview]
Message-ID: <20200518010131.GM6362@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAP16ngpd_GbfUkSuBks5jk2vskks5_SRmVHOmfaEUTLoWiD8hQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
On 2020-05-17 at 21:58:41, bruce wrote:
> Hi.
>
> Hope this is a place to ask this.
>
> There are lots of foo.git files.
>
> I'm trying to figure out what's un a git file. As an example,
> gets the drupal repos.
> However, I can't seem to find the drupal.git file. Even a net search
> doesnt seem to turn up a file that I can view!!
>
> Any pointers/thoughts would be helpful.
The ending ".git" is just a conventional approach to indicate that a URL
or directory is a bare repository. When using HTTP, the actual files
are served from other locations, depending on whether the site is using
the smart or dumb HTTP protocol. Most major hosting platforms prefer
the smart protocol because it can send a lot less data.
So there really isn't a single file; instead, there's either some static
files and some manifests (for the dumb protocol) or conversations with a
CGI client (for the smart protocol). You can read more about it in
Documentation/technical/http-protocol.txt, and if you're interested, you
can run your operations with GIT_CURL_VERBOSE=1 to see the endpoints
that are contacted. (Be aware that that output may contain
credentials.)
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2020-05-18 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 21:58 contents of a .git file bruce
2020-05-18 1:01 ` brian m. carlson [this message]
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=20200518010131.GM6362@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=badouglas@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).