From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, spearce@spearce.org, sasa.zivkov@sap.com
Subject: Re: [PATCH] Don't create the $GIT_DIR/branches directory on init
Date: Sat, 31 Oct 2009 19:02:47 +0100 [thread overview]
Message-ID: <200910311902.48317.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <200910311011.31189.trast@student.ethz.ch>
lördag 31 oktober 2009 10:11:29 skrev Thomas Rast:
> Robin Rosenberg wrote:
> > Git itself does not even look at this directory.
>
> This contradicts the git-fetch manpage though: from urls-remotes.txt,
> it includes
>
> 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.
>
> (and a longer explanation of what they need to look like).
>
> So which one is wrong?
I, and a few other people, it seems. Seems the purpose of these
files is a bit different. Git does look in these directories (both)
when fetch is run. Seems remotes is not created by init though.
-- robin
next prev parent reply other threads:[~2009-10-31 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 17:20 [PATCH] Don't create the $GIT_DIR/branches directory on init Robin Rosenberg
2009-10-30 21:35 ` Junio C Hamano
2009-10-31 9:11 ` Thomas Rast
2009-10-31 18:02 ` Robin Rosenberg [this message]
2009-10-31 18:09 ` Shawn O. Pearce
2009-10-31 18:15 ` Junio C Hamano
2009-10-31 18:24 ` Shawn O. Pearce
2009-10-31 19:32 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200910311902.48317.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sasa.zivkov@sap.com \
--cc=spearce@spearce.org \
--cc=trast@student.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.