From: Dotan Barak <dotanba@gmail.com>
To: Kristian Amlie <kristian.amlie@nokia.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: How can i find the origin of a branch?
Date: Mon, 15 Jun 2009 16:34:30 +0300 [thread overview]
Message-ID: <2f3bf9a60906150634p18e67e71q6e5e7cbb8df1d8c4@mail.gmail.com> (raw)
In-Reply-To: <2f3bf9a60906150503p69e992b4m18bdc2cc842b933e@mail.gmail.com>
Thanks, your suggestion helped, but there is one problem:
I noticed that if there is only one branch, the entry
branch.<branch_name>.merge doesn't exist.
Even if there is more than one remote URLs.
Dotan
On Mon, Jun 15, 2009 at 3:03 PM, Dotan Barak<dotanba@gmail.com> wrote:
> Thank you very much for a quick and exact answer
> :)
>
> Dotan
>
>
> On Mon, Jun 15, 2009 at 2:57 PM, Kristian Amlie<kristian.amlie@nokia.com> wrote:
>> ext Dotan Barak wrote:
>>> Hi.
>>>
>>> Is it possible to find the origin of a branch?
>>> (the remote repository that this branch was cloned and checked out from)
>>
>> git config -l
>>
>> Assuming you're on the master branch, branch.master.remote and
>> branch.master.merge will tell you which remote and which branch you are
>> tracking. Assuming that the remote is origin, you can check
>> remote.origin.url to see the URL of the repo.
>>
>> --
>> Kristian
>>
>
next prev parent reply other threads:[~2009-06-15 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 11:37 How can i find the origin of a branch? Dotan Barak
2009-06-15 11:57 ` Kristian Amlie
2009-06-15 12:03 ` Dotan Barak
2009-06-15 13:34 ` Dotan Barak [this message]
2009-06-15 12:48 ` Alex Riesen
2009-06-15 13:10 ` Kristian Amlie
2009-06-15 12:07 ` Alex Riesen
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=2f3bf9a60906150634p18e67e71q6e5e7cbb8df1d8c4@mail.gmail.com \
--to=dotanba@gmail.com \
--cc=git@vger.kernel.org \
--cc=kristian.amlie@nokia.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).