From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-fetch: Allow branch."branchname".remote=.
Date: Fri, 13 Oct 2006 15:06:07 +0200 [thread overview]
Message-ID: <ego2vm$568$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0610131448390.14200@wbgn013.biozentrum.uni-wuerzburg.de
<opublikowany i wysłany>
Johannes Schindelin wrote:
> On Fri, 13 Oct 2006, Jakub Narebski wrote:
>
>> Johannes Schindelin wrote:
>>
>> > There is a subtle problem here. Up until now, "remote" meant a short cut.
>> > You either had a file with that name in .git/remotes/ or .git/branches, or
>> > an entry in the config (remote.<name>.url).
>>
>> Not exactly. "git-pull . <branch>" and "git-peek-remote ." meant use
>> _current_ repository. "." as remote name means "current", i.e. local
>> repository.
>
> From Documentation/git-pull.txt:
>
> SYNOPSIS
> --------
> 'git-pull' <options> <repository> <refspec>...
>
> It says "repository", not "remote". As for the name "git-peek-remote":
> yes, it is a short cut for "remote repository".
>
> The thing is, if you say you pull "from a remote", then it is not
> sufficient to specify just a URL of a repository. You also have to specify
> a branch.
O.K. "remote" = "repository + set of branches". But we can say that "."
is a default remote, which points to local repository (".") and has
no branches information.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-10-13 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 7:50 [PATCH] git-fetch: Allow branch."branchname".remote= Santi Béjar
2006-10-13 7:56 ` Junio C Hamano
2006-10-13 9:08 ` Santi
2006-10-13 11:27 ` Johannes Schindelin
2006-10-13 12:39 ` Jakub Narebski
2006-10-13 12:53 ` Johannes Schindelin
2006-10-13 13:06 ` 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='ego2vm$568$1@sea.gmane.org' \
--to=jnareb@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.
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.