Alexander Kojevnikov wrote:
> The site now features Atom feeds for the following files:
>
> * ports/UPDATING
> * head/UPDATING
> * stable/7/UPDATING
> * stable/8/UPDATING
>
> Hope you find the feeds useful.
Useful indeed! Also, this is probably a nice thread to point out that a
commit log feed e
2010/9/25 jhell :
> On 09/25/2010 09:24, Alexander Kojevnikov wrote:
>> On 25 September 2010 17:04, Alexander Kojevnikov
>> wrote:
>>> On 25 September 2010 15:44, jhell wrote:
Really awesome!
This will come in handy to serve up stable/*/UPDATING and head/UPDATING
to. And think
On 09/25/2010 09:24, Alexander Kojevnikov wrote:
> On 25 September 2010 17:04, Alexander Kojevnikov
> wrote:
>> On 25 September 2010 15:44, jhell wrote:
>>> Really awesome!
>>>
>>> This will come in handy to serve up stable/*/UPDATING and head/UPDATING
>>> to. And thinking along those lines it co
On 25 September 2010 17:04, Alexander Kojevnikov
wrote:
> On 25 September 2010 15:44, jhell wrote:
>> Really awesome!
>>
>> This will come in handy to serve up stable/*/UPDATING and head/UPDATING
>> to. And thinking along those lines it could probably be incorporated
>> directly into the DAV tree
to upgrade from FreeBSD-current previous to GCC3.1 (circa April, May) to the
current top of tree, a 'make -k world' may be necessary to skip over an
(apparently unnecessary) broken gperf build.
This has been confirmed twice for alpha and once for i386.
To Unsubscribe: send mail to [EMAIL PROT
In message: <[EMAIL PROTECTED]>
Julian Elischer <[EMAIL PROTECTED]> writes:
: Who's doing UPDATING now?
Nobody owns it. I've committed your change. I have a few more
changes I should commit.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
Who's doing UPDATING now?
can someone who is allowed to commit to it put in a note that right now
might be a bad time to upgade if you want to use anything that uses
libc_r. Either libc_r or KSE is causing problems. I don't yet know which.
Things that use libc_r include KDE and GNOME apparentl
On Sat, Oct 06, 2001 at 12:32:20AM +1000, Andrew Kenneth Milton wrote:
> Nevermind d8). I've updated the code for vmware2, and the drm-kmod ports, and
> have contacted the maintainers. So hopefully the code will go into the
> relevant ports soon.
I already posted patches for vmware on Sept 14; be
+---[ Andrew Kenneth Milton ]--
| Is there a script for updating sources from pre-kse to post-kse status?
|
| Both the vmware ports, and drm ports all need some work done to bring them up
| to scratch with the KSE changes.
|
| So is there a tool, or does it all have to
Is there a script for updating sources from pre-kse to post-kse status?
Both the vmware ports, and drm ports all need some work done to bring them up
to scratch with the KSE changes.
So is there a tool, or does it all have to be done manually?
--
Totally Holistic Enterprises Internet
10 matches
Mail list logo