Something wrong with the svn0.eu.freebsd.org mirror:
svn: E60: Unable to connect to a repository at URL
'https://svn0.eu.freebsd.org/base/head'
svn: E60: Error running context: Operation timed out
I hope it's temprorary problem, but
please advise if the mirror address has
changed.
Thank
TB --- 2014-02-06 10:10:18 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2014-02-06 10:10:18 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2014
On Thu, Feb 06, 2014 at 01:07:50AM -0800, Anton Shterenlikht wrote:
> Something wrong with the svn0.eu.freebsd.org mirror:
>
> svn: E60: Unable to connect to a repository at URL
> 'https://svn0.eu.freebsd.org/base/head'
> svn: E60: Error running context: Operation timed out
>
This shoul
>From g...@freebsd.org Thu Feb 6 15:34:12 2014
>
>On Thu, Feb 06, 2014 at 01:07:50AM -0800, Anton Shterenlikht wrote:
>> Something wrong with the svn0.eu.freebsd.org mirror:
>>=20
>> svn: E60: Unable to connect to a repository at URL 'https://svn0.eu.f=
>reebsd.org/base/head'
>> svn: E60:
06.02.2014 06:00, Yonghyeon PYUN пишет:
> On Sat, Feb 01, 2014 at 12:18:59PM +0400, Boris Samorodov wrote:
>> Hi Yonghyeon and All,
>>
>> (this time it's a CURRENT issue)
>>
>> 31.10.2013 17:33, Boris Samorodov пишет:
>>> 30.10.2013 06:16, Yonghyeon PYUN пишет:
On Tue, Oct 29, 2013 at 05:38:27
Yonghyeon PYUN wrote:
> On Mon, Feb 03, 2014 at 02:56:37PM +0100, Christian Brueffer wrote:
> > Hi,
> >
> > for some time now we have had two drivers for NVIDIA NForce/MCP network
> > chips, namely nve(4) and nfe(4).
> >
> > The former came first and is based on a binary blob. The latter was
> >
On 6 Feb 2014, at 18:34, Julian H. Stacey wrote:
> Best avoid the obscure word `Deprecated' in manuals:
> It's not common/ plain English. Maybe a geek import, or USA
> dialect ? It's not easily internationaly understood English.
> Best make manuals easier for non native English speakers (& n
On Thu, Feb 6, 2014 at 6:34 PM, Julian H. Stacey wrote:
> Best avoid the obscure word `Deprecated' in manuals:
> It's not common/ plain English. Maybe a geek import, or USA
> dialect ? It's not easily internationaly understood English.
> Best make manuals easier for non native English spea
I have a patch to teach the PCI bus code and PCI-PCI bridge driver to manage
PCI bus numbers. The approach is somewhat similar to how NEW_PCIB manages I/O
windows for briges. Each bridge creates an rman to manage the bus numbers for
all buses and bridges that live below it. Each bus allocates
On Thu, Feb 6, 2014 at 2:37 PM, John Baldwin wrote:
> I have a patch to teach the PCI bus code and PCI-PCI bridge driver to
> manage
> PCI bus numbers. The approach is somewhat similar to how NEW_PCIB manages
> I/O
> windows for briges. Each bridge creates an rman to manage the bus numbers
> fo
On Thu, Feb 6, 2014 at 2:47 PM, Thomas Hoffmann wrote:
> On Thu, Feb 6, 2014 at 2:37 PM, John Baldwin wrote:
>
>> I have a patch to teach the PCI bus code and PCI-PCI bridge driver to
>> manage
>> PCI bus numbers. The approach is somewhat similar to how NEW_PCIB
>> manages I/O
>> windows for br
On Thursday, February 06, 2014 2:47:09 pm Thomas Hoffmann wrote:
> On Thu, Feb 6, 2014 at 2:37 PM, John Baldwin wrote:
>
> > I have a patch to teach the PCI bus code and PCI-PCI bridge driver to
> > manage
> > PCI bus numbers. The approach is somewhat similar to how NEW_PCIB manages
> > I/O
> >
centage of language experience internal
national usage.
FreeBSD's manual writers, especially non native English manual
writers, should not copy Americanisms &/or bad nomenclature from
one manual to another, but ask themselves if they know better words,
to make it easier also for other non n
On 02/06/14 14:37, John Baldwin wrote:
I have a patch to teach the PCI bus code and PCI-PCI bridge driver to
manage PCI bus numbers. The approach is somewhat similar to how
NEW_PCIB manages I/O windows for briges. Each bridge creates an rman
to manage the bus numbers for all buses and bridges t
ce internal
> national usage.
>
> FreeBSD's manual writers, especially non native English manual
> writers, should not copy Americanisms &/or bad nomenclature from
> one manual to another, but ask themselves if they know better words,
> to make it easier also for other non
15 matches
Mail list logo