From: Jakub Narebski <jnareb@gmail.com>
To: Ron Garret <ron1@flownet.com>
Cc: git@vger.kernel.org
Subject: Re: Is ./git/branches used for anything?
Date: Tue, 02 Feb 2010 07:00:09 -0800 (PST) [thread overview]
Message-ID: <m34olzbs5f.fsf@localhost.localdomain> (raw)
In-Reply-To: <ron1-35461E.00013102022010@news.gmane.org>
Ron Garret <ron1@flownet.com> writes:
> If so, what? .git/refs/heads seems to contain all the branch info, so
> what is the branches directory for?
See gitrepository-layout(5):
branches::
A slightly deprecated way to store shorthands to be used
to specify URL to 'git fetch', 'git pull' and 'git push'
commands is to store a file in `branches/<name>` and
give 'name' to these commands in place of 'repository'
argument.
and git-pull(1):
REMOTES
-------
The name of one of the following can be used instead
of a URL as `<repository>` argument:
* a remote in the git configuration file: `$GIT_DIR/config`,
* a file in the `$GIT_DIR/remotes` directory, or
* a file in the `$GIT_DIR/branches` directory.
All of these also allow you to omit the refspec from the command line
because they each contain a refspec which git will use by default.
[...]
Named file in `$GIT_DIR/branches`
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can choose to provide the name of a
file in `$GIT_DIR/branches`.
The URL in this file will be used to access the repository.
This file should have the following format:
------------
<url>#<head>
------------
`<url>` is required; `#<head>` is optional.
Depending on the operation, git will use one of the following
refspecs, if you don't provide one on the command line.
`<branch>` is the name of this file in `$GIT_DIR/branches` and
`<head>` defaults to `master`.
Ancient history, if somewhat useful for some workflow[1]. It came from
Cogito, which was alternate UI for git.
[1] Namely one of main Linux kernel developers (Linus lieutienants)
has scripts around this way of specifying remote information.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2010-02-02 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 8:01 Is ./git/branches used for anything? Ron Garret
2010-02-02 8:11 ` Sverre Rabbelier
2010-02-02 8:19 ` Ron Garret
2010-02-02 15:00 ` Jakub Narebski [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m34olzbs5f.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=ron1@flownet.com \
/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).