netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: Netdev <netdev@oss.sgi.com>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: git repository for net drivers available
Date: Fri, 13 May 2005 11:29:30 -0400	[thread overview]
Message-ID: <4284C7DA.1020707@pobox.com> (raw)
In-Reply-To: <4284C54E.3060907@linux.intel.com>

James Ketrenos wrote:
> Jeff Garzik wrote:
> 
> 
>>This includes the wireless-2.6 repository.
>>
>>rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
>>
>>The main branch is fairly irrelevant, as you must choose the branch
>>you wish:
>>
>>
>>>[jgarzik@pretzel netdev-2.6]$ ls .git/branches/
>>>8139cp         e1000        ixgb     r8169            skge          
>>>we18
>>>8139too-iomap  forcedeth    janitor  register-netdev  smc91x        
>>>wifi
>>>amd8111        ieee80211    orinoco  remove-drivers   smc91x-eeprom
>>>e100           iff-running  ppp      sis900           starfire
>>
> Ok, I'll bite.  Hopefully I'm not the only one tripping on shoe laces...
> 
> Here is what I did -- what am I doing wrong?
> 
> Following is using cogito 0.10:
> 
> REPO=rsync://rsync.kernel.org/pubs/scm/linux/kernel/git/jgarzik/netdev-2.6.git
> cg-clone ${REPO}
> .... get coffee, etc. ... come back and I have a netdev-2.6 tree ...
> cg-branch-add wifi ${REPO}#wifi
> cg-update wifi
> .... connects and attempts to download but fails out with:
> 
> ----------------
> receiving file list ... done
> client: nothing to do: perhaps you need to specify some filenames or the
> --recursive option?
> 
> rsync: link_stat
> "/scm/linux/kernel/git/jgarzik/netdev-2.6.git/heads/wifi" (in pub)
> failed: No such file or directory (2)

Looks like cogito is using $repo/heads/$branch, whereas my git repo is 
using $repo/branches/$branch.

You can achieve what's necessary with

> rsync --verbose --delete --stats --progress \
> -a rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git/ .git

and then

> ( cd .git ; rm -f HEAD ; ln -s branches/wifi HEAD )

and then

> git-read-tree $(cat .git/HEAD) && git-checkout-cache -q -f -a && git-update-cache --refresh



For what it's worth, this is only netdev-2.6 as it appeared in 
BitKeeper.  I am only now merging all the emailed patches since BK devel 
stopped into git, which includes the ipw code you submitted.

	Jeff

  reply	other threads:[~2005-05-13 15:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13  3:08 git repository for net drivers available Jeff Garzik
2005-05-13 15:18 ` James Ketrenos
2005-05-13 15:29   ` Jeff Garzik [this message]
2005-05-15 20:05     ` Petr Baudis
2005-05-15 20:20       ` Jeff Garzik
2005-05-14 10:57 ` Krzysztof Halasa
2005-05-14 14:02   ` 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=4284C7DA.1020707@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=jketreno@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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).