From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Show remote branches on gitweb
Date: Sat, 25 Nov 2006 01:12:55 +0100 [thread overview]
Message-ID: <ek81mv$qd8$1@sea.gmane.org> (raw)
In-Reply-To: 20061124235911.GO7201@pasky.or.cz
Petr Baudis wrote:
> On Fri, Nov 24, 2006 at 09:56:29PM CET, Jakub Narebski wrote:
>> Jakub Narebski wrote:
>>
>>> Pazu wrote:
>>>
>>>> Is there any way to do it? I'm using git-svn to track a remote subversion
>>>> repository, and it would be very nice to browse the history for a remote branch
>>>> for which I didn't start a local branch yet.
>>>
>>> Planned, not implemented yet.
>>
>> The problem is that to implement it _well_ we have to get remotes, both
>> $GIT_DIR/remotes and config remote.xxx, info. And the latter (config
>> remotes info) needs config parsing, something we lack.
>
> Does that mean we _can_ parse $GIT_DIR/remotes? ;-)
No, but for implementing showing remote branches in gitweb _well_,
but without frills'n'whistles, it is enough to know files in
$GIT_DIR/remotes (Find::find those files), and don't need to parse
remotes/ files.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-11-25 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 20:06 Show remote branches on gitweb Pazu
2006-11-24 20:17 ` Jakub Narebski
2006-11-24 20:56 ` Jakub Narebski
2006-11-24 23:59 ` Petr Baudis
2006-11-25 0:12 ` Jakub Narebski [this message]
2006-11-25 0:40 ` Junio C Hamano
2006-11-25 0:50 ` Petr Baudis
2006-11-25 1:04 ` Junio C Hamano
2006-11-28 15:14 ` Jakub Narebski
2006-11-27 19:20 ` Pazu
2006-11-27 19:26 ` Jakub Narebski
2006-11-28 2:59 ` Pazu
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='ek81mv$qd8$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.