From: Petr Baudis <pasky@suse.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Anand Kumria <wildfire@progsoc.org>, git@vger.kernel.org
Subject: Re: when is a remote a branch?
Date: Tue, 14 Nov 2006 21:44:10 +0100 [thread overview]
Message-ID: <20061114204410.GK7201@pasky.or.cz> (raw)
In-Reply-To: <200611142136.17517.jnareb@gmail.com>
On Tue, Nov 14, 2006 at 09:36:16PM CET, Jakub Narebski wrote:
> Petr "Pasky" Baudis wrote:
> > On Sun, Nov 12, 2006 at 06:31:18PM CET, Jakub Narebski wrote:
> >>
> >> By the way, with introduction of branches and remotes in config file,
> >> you can say:
> >> [branch "localbranch"]
> >> remote = someremote
> >> [remote "someremote"]
> >> fetch = remotebranch:localbranch
> >> push = remotebranch:localbranch
> >>
> >> and that would be equivalent to example branches file from
> >> the beginning of this email.
> >
> > According to the documentation, this is not really useful since this
> > just tells what should git fetch default to when on branch
> > "localbranch". But "localbranch" is still just a branch representing a
> > state in a remote repository, so you should never be _on_ it in a sane
> > setup, but instead on a different branch which tracks it.
>
> Oh. Can you "git fetch Localbranch" _without_ repository named
> "localbranch" in above case?
So that it would be equivalent to git fetch someremote, and also fetch
any other branches associated with that remote?
I would hope not. :-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
prev parent reply other threads:[~2006-11-14 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 15:50 when is a remote a branch? Anand Kumria
2006-11-12 16:11 ` Jakub Narebski
2006-11-12 16:36 ` Petr Baudis
2006-11-12 17:31 ` Jakub Narebski
2006-11-14 20:28 ` Petr Baudis
2006-11-14 20:36 ` Jakub Narebski
2006-11-14 20:44 ` Petr Baudis [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=20061114204410.GK7201@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=wildfire@progsoc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox