From: Larry Finger <larry.finger@lwfinger.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: ALERT: firmware change for b43
Date: Thu, 23 Aug 2007 17:16:55 -0500 [thread overview]
Message-ID: <46CE0757.8000008@lwfinger.net> (raw)
In-Reply-To: <1187860330.22432.139.camel@pmac.infradead.org>
David Woodhouse wrote:
> On Sun, 2007-08-19 at 14:37 -0500, Larry Finger wrote:
>> It is recommended that you update fwcutter before these patches are
>> merged. If your version of fwcutter was obtained with subversion, a
>> simple 'svn update' in the fwcutter directory will suffice.
>> If you are using a version provided by your distro, you will need to
>> checkout the latest version with the command 'svn checkout
>> svn://svn.berlios.de/bcm43xx/trunk/fwcutter'.
>
> Ew, Subversion. Hasn't everyone abandoned that yet?
>
> I've set up a script to mirror it into git hourly:
> http://git.infradead.org/?p=b43-fwcutter.git
> git://git.infradead.org/b43-fwcutter.git
>
Although git is clearly superior, it doesn't make that much difference for small projects. Where
Subversion still has a place, however, is where the project is code used on multiple OS's. At least
I haven't seen a port of git to Windows. OS X wouldn't be that much trouble, I guess.
Larry
prev parent reply other threads:[~2007-08-23 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 19:37 ALERT: firmware change for b43 Larry Finger
2007-08-22 14:52 ` John W. Linville
2007-08-22 15:25 ` Larry Finger
2007-08-22 17:18 ` John W. Linville
2007-08-22 18:08 ` Larry Finger
2007-08-22 18:10 ` John H.
2007-08-22 18:20 ` Larry Finger
2007-08-22 22:28 ` Michael Buesch
2007-08-23 9:12 ` David Woodhouse
2007-08-23 20:57 ` Michael Buesch
2007-08-23 22:16 ` Larry Finger [this message]
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=46CE0757.8000008@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=dwmw2@infradead.org \
--cc=linux-wireless@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.