git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: FTP Admin <ftpadmin@kernel.org>, Kay Sievers <kay.sievers@vrfy.org>
Subject: gitweb and kernel.org
Date: Fri, 20 May 2005 13:48:32 -0400	[thread overview]
Message-ID: <428E22F0.3050007@pobox.com> (raw)


No sure who maintains http://www.kernel.org/git/ so...

I have a request for the above URL:  provide access to branches in 
refs/heads/* somehow.  -All- my work occurs in a branch, with the main 
branch containing nothing but "vanilla Linus" tree.

My jgarzik/libata-dev.git repository contains a large number of branches:
> [jgarzik@pretzel libata-dev]$ ls .git/refs/heads/
> adma        atapi-enable        iomap        new-ids   promise-sata-pata
> adma-mwi    bridge-detect       iomap-step1  passthru  sil24
> ahci-atapi  chs-support         master       pdc2027x
> ahci-msi    ioctl-get-identity  misc-fixes   pdc20619

and ditto for jgarzik/netdev-2.6.git:
> [jgarzik@pretzel netdev-2.6]$ ls .git/refs/heads/
> 8139cp         e100         janitor      pcnet32          skge           we18
> 8139too-iomap  e1000        master       ppp              smc91x         wifi
> airo           forcedeth    misc-fixes   qeth             smc91x-eeprom
> amd8111        hdlc         natsemi      r8169            starfire
> atmel          ieee80211    ns83820      register-netdev  tlan
> chelsio        iff-running  orinoco      remove-drivers   veth
> dm9000         ixgb         orinoco-hch  sis900           viro


             reply	other threads:[~2005-05-20 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 17:48 Jeff Garzik [this message]
2005-05-20 18:58 ` gitweb and kernel.org Kay Sievers
2005-05-20 19:47   ` Jeff Garzik

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=428E22F0.3050007@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=ftpadmin@kernel.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).