"Jordan K. Hubbard" wrote:
>
> > > Maybe the comitters ought to take an idea from many software companies and
> > > contribute $5 to the beer fund every time they break the build. Have it
> > > all come due at the next BSDcon to fund a committer beer bash. :-)
> >
> > I'd go along with that. Wh
On Mon, May 15, 2000 at 09:21:54PM -0700, Jordan K. Hubbard wrote:
> > > Maybe the comitters ought to take an idea from many software companies and
> > > contribute $5 to the beer fund every time they break the build. Have it
> > > all come due at the next BSDcon to fund a committer beer bash. :-
> > Maybe the comitters ought to take an idea from many software companies and
> > contribute $5 to the beer fund every time they break the build. Have it
> > all come due at the next BSDcon to fund a committer beer bash. :-)
>
> I'd go along with that. What do the other committers think?
I th
> Darren Reed wrote:
> >
> > > > Maybe the comitters ought to take an idea from many software companies and
> > > > contribute $5 to the beer fund every time they break the build. Have it
> > > > all come due at the next BSDcon to fund a committer beer bash. :-)
> > >
> > > I'd go along with tha
Darren Reed wrote:
>
> > > Maybe the comitters ought to take an idea from many software companies and
> > > contribute $5 to the beer fund every time they break the build. Have it
> > > all come due at the next BSDcon to fund a committer beer bash. :-)
> >
> > I'd go along with that. What do th
On Monday, 15 May 2000 at 13:48:19 +1000, Darren Reed wrote:
> In some email I received from Greg Lehey, sie wrote:
>> On Sunday, 14 May 2000 at 23:21:21 -0400, Tim Vanderhoek wrote:
>>> On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote:
>>> Maybe the comitters ought to take
Hi all,
I think I might have an even better solution. Continue passing
the pointy hat around & I'll buy the committer's keg at the
next BSDcon. I for one appreciate the exceptional funcitionality
of FreeBSD (especially the IPSec support). And also, if I buy the
key, maybe I'll also be invited.
R
In some email I received from Greg Lehey, sie wrote:
> On Sunday, 14 May 2000 at 23:21:21 -0400, Tim Vanderhoek wrote:
> > On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote:
> >>
> > Maybe the comitters ought to take an idea from many software companies and
> > contribute $5 t
On Sunday, 14 May 2000 at 23:21:21 -0400, Tim Vanderhoek wrote:
> On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote:
>>
> Maybe the comitters ought to take an idea from many software companies and
> contribute $5 to the beer fund every time they break the build. Have it
>
On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote:
>
Maybe the comitters ought to take an idea from many software companies and
contribute $5 to the beer fund every time they break the build. Have it
all come due at the next BSDcon to fund a committer beer bash. :-)
>>
On Sun, May 14, 2000 at 11:06:50AM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Greg Lehey writes:
> : > Maybe the comitters ought to take an idea from many software companies and
> : > contribute $5 to the beer fund every time they break the build. Have it
> : > all come due at the
On Sun, May 14, 2000 at 10:19:21AM +0930, Greg Lehey wrote:
> I'd go along with that. What do the other committers think?
Can I drink pop instead? I'm underage, and I don't like alcohol anyway. :)
--
Will Andrews <[EMAIL PROTECTED]>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N
In message <[EMAIL PROTECTED]> Greg Lehey writes:
: > Maybe the comitters ought to take an idea from many software companies and
: > contribute $5 to the beer fund every time they break the build. Have it
: > all come due at the next BSDcon to fund a committer beer bash. :-)
:
: I'd go along wit
Mike Nowlin wrote:
>
> > I'd just seen a series of bad commits whose corrections weren't caught by the
> > frequency of my cvs updates I guees. Vinum is compiling now, and kernels with
> > IPSEC and INETV6 now link, it's just that last night's problems with more got
> > me a little ticked off.
>
> > > Maybe the comitters ought to take an idea from many software companies and
> > > contribute $5 to the beer fund every time they break the build. Have it
> > > all come due at the next BSDcon to fund a committer beer bash. :-)
> >
> > I'd go along with that. What do the other committers th
In some email I received from Greg Lehey, sie wrote:
> On Saturday, 13 May 2000 at 9:53:40 -0700, Brian W. Buchanan wrote:
> > On Fri, 12 May 2000, Stephen Hocking wrote:
> >
> >> For the past few days, current has not compiled, owing to problems (in no
> >> particular order) with more, vinum and
On Saturday, 13 May 2000 at 9:53:40 -0700, Brian W. Buchanan wrote:
> On Fri, 12 May 2000, Stephen Hocking wrote:
>
>> For the past few days, current has not compiled, owing to problems (in no
>> particular order) with more, vinum and various INET options in the GENERIC
>> kernel. Can people plea
On Fri, 12 May 2000, Stephen Hocking wrote:
> For the past few days, current has not compiled, owing to problems (in no
> particular order) with more, vinum and various INET options in the GENERIC
> kernel. Can people please check things before they commit them? I like a
> working compile at l
> I'd just seen a series of bad commits whose corrections weren't caught by the
> frequency of my cvs updates I guees. Vinum is compiling now, and kernels with
> IPSEC and INETV6 now link, it's just that last night's problems with more got
> me a little ticked off.
>
> cc: main.c: No such file
> This is the first I've heard of a problem in Vinum.
>
> > Can people please check things before they commit them? I like a
> > working compile at least *once* a week.
>
> I'm wondering if you haven't had some other problem. I haven't heard
> anybody else with problems.
>
I have a number of
On Friday, 12 May 2000 at 23:35:09 +0800, Stephen Hocking wrote:
> For the past few days, current has not compiled, owing to problems (in no
> particular order) with more, vinum and various INET options in the GENERIC
> kernel.
This is the first I've heard of a problem in Vinum.
> Can people ple
For the past few days, current has not compiled, owing to problems (in no
particular order) with more, vinum and various INET options in the GENERIC
kernel. Can people please check things before they commit them? I like a
working compile at least *once* a week.
Stephen
--
The views
22 matches
Mail list logo
