From: sean <seanlkml@sympatico.ca>
To: David Woodhouse <dwmw2@infradead.org>
Cc: kay.sievers@vrfy.org, git@vger.kernel.org
Subject: Re: Two gitweb feature requests
Date: Fri, 28 Apr 2006 12:26:30 -0400 [thread overview]
Message-ID: <BAYC1-PASMTP0240D4E75F0F6EE37BA4EBAEB20@CEZ.ICE> (raw)
Message-ID: <20060428122630.234edde4.seanlkml@sympatico.ca> (raw)
In-Reply-To: <1146144425.11909.450.camel@pmac.infradead.org>
On Thu, 27 Apr 2006 14:27:05 +0100
David Woodhouse <dwmw2@infradead.org> wrote:
> First... When publishing trees, I currently give both the git:// URL for
> people who want to pull the tree, and the http:// URL to gitweb for
> those who just want to browse.
>
> It would be useful if I could get away with giving just one URL --
> probably the http:// one to gitweb. If gitweb were to have a mode in
> which it gave a referral to the git:// URL, and if the git tools would
> use that, then that would work well.
This sounds like a good idea.
> Secondly, it would be useful if gitweb would list the branches in a
> repository and allow each of them to be viewed in the same way as it
> does the master branch.
At the bottom of the Summary page it already lists the branches,
underneath the tags.
Sean
next prev parent reply other threads:[~2006-04-28 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 13:27 Two gitweb feature requests David Woodhouse
2006-04-27 13:35 ` Matthias Lederhofer
2006-04-27 13:47 ` David Woodhouse
2006-04-27 22:54 ` Ben Clifford
2006-04-29 21:38 ` David Woodhouse
[not found] ` <20060428122630.234edde4.seanlkml@sympatico.ca>
2006-04-28 16:26 ` sean [this message]
2006-04-28 17:37 ` Jakub Narebski
2006-04-28 18:23 ` Linus Torvalds
2006-04-28 19:11 ` Jakub Narebski
2006-04-29 5:02 ` Jeff King
2006-04-29 11:16 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2006-04-29 7:27 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=BAYC1-PASMTP0240D4E75F0F6EE37BA4EBAEB20@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.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;
as well as URLs for NNTP newsgroup(s).