From: Pavel Roskin <proski@gnu.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Removing .tmp_versions considered harmful
Date: Mon, 24 Apr 2006 16:19:36 -0400 [thread overview]
Message-ID: <1145909976.2292.52.camel@dv> (raw)
In-Reply-To: <1145908684.3116.65.camel@laptopd505.fenrus.org>
Hello!
On Mon, 2006-04-24 at 21:58 +0200, Arjan van de Ven wrote:
> On Mon, 2006-04-24 at 15:55 -0400, Pavel Roskin wrote:
> > Hello, Sam!
> >
> > How about following patch? Something needs to be done before 2.6.17.
> > Complaints about .tmp_versions are almost in every list about wireless
> > drivers I'm subscribed to.
>
> seems all wireless drivers stole eachothers broken makefiles then ;)
There is is some similarity, and it's a good thing.
> Makes it also easy to fix I suppose
Could you please elaborate? How can it be fixed? Do you know any
external module that doesn't have this problem?
If you have a could of minutes, please look at Orinoco, which probably
has the simplest build system, yet it suffers from the .tmp_versions
problem. The Subversion repository is here
http://sourceforge.net/svn/?group_id=44338
To check the main development branch, please use
svn co https://svn.sourceforge.net/svnroot/orinoco/trunk orinoco
This is the Makefile:
http://svn.sourceforge.net/viewcvs.cgi/*checkout*/orinoco/trunk/Makefile
What would you fix?
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-04-24 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 4:22 Removing .tmp_versions considered harmful Pavel Roskin
2006-04-21 7:32 ` Sam Ravnborg
2006-04-21 11:55 ` Pavel Roskin
2006-04-24 19:55 ` Pavel Roskin
2006-04-24 19:58 ` Arjan van de Ven
2006-04-24 20:19 ` Pavel Roskin [this message]
2006-04-30 21:47 ` Sam Ravnborg
2006-05-01 0:59 ` Pavel Roskin
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=1145909976.2292.52.camel@dv \
--to=proski@gnu.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.