From: "Alexander Litvinov" <litvinov2004@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Getting new branches from remote repo.
Date: Mon, 13 Nov 2006 11:29:25 +0600 [thread overview]
Message-ID: <6e1787fe0611122129l211f7bcaued9f4981225a241b@mail.gmail.com> (raw)
In-Reply-To: <7v8xigar36.fsf@assigned-by-dhcp.cox.net>
> After finding out $that_new_branch's name, add either
>
> Pull: refs/heads/$that_new_branch:refs/heads/$that_new_branch
> You would still see them if you say "ls-remote" without --heads.
Thanks for help, these commands solve my trouble:
1. Get remote branches by 'git ls-remote origin refs/remotes/*'
2. Fetch needed branch by adding: 'Pull:
refs/remotes/origin/BRANCH:refs/heads/BRANCH' into .git/remotes/origin
Is there any way to automaticly edit .git/remotes/origin before
next prev parent reply other threads:[~2006-11-13 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 4:33 Getting new branches from remote repo Alexander Litvinov
2006-11-13 4:49 ` Junio C Hamano
2006-11-13 5:29 ` Alexander Litvinov [this message]
2006-11-13 9:17 ` Karl Hasselström
2006-11-13 16:57 ` Matthias Hopf
2006-11-13 17:44 ` Shawn Pearce
2006-11-13 17:53 ` Karl Hasselström
2006-11-13 18:17 ` Junio C Hamano
2006-11-13 18:40 ` Jakub Narebski
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=6e1787fe0611122129l211f7bcaued9f4981225a241b@mail.gmail.com \
--to=litvinov2004@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).