Give contact details for immediate fund transfer...
Sent from my Windows Phone
-----Original Message-----
From: Pierre Schweitzer
Sent: 22-09-2013 PM 04:31
To: ReactOS Development List
Subject: Re: [ros-dev] reactos.org is down
Your offer to pay a full-time sysadmins team (4 is fine), with on-call
time for the next year has been well received.
Thanks as well to offer us two more machines to ensure this never
happens again.
Please contact ReactOS Deutschland e.V. for fund transfert information.
Such considerable efforts are never forgotten.
On 22/09/2013 12:39, Ameer Ali wrote:
> Makesure that reactos.org site is available at everytime.Many activity got
> pending due to this. Don't repeat.
>
> Provide action plan for the same.urgent
>
> Sent from my Linux Phone
> ------------------------------
> From: Pierre Schweitzer
> Sent: 22-09-2013 PM 03:26
> To: ros-dev(a)reactos.org
> Subject: Re: [ros-dev] reactos.org is down
>
> Hi,
>
> we're currently getting back online.
>
> Sorry for the inconvenience caused by this downtime.
>
> With my best regards,
>
> On 22/09/2013 11:25, Александр wrote:
>
> reactos.org is down
--
Pierre Schweitzer<pierre at reactos.org>
System Administrator
ReactOS Foundation
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Makesure that reactos.org site is available at everytime.Many activity got
pending due to this. Don't repeat.
Provide action plan for the same.urgent
Sent from my Linux Phone
------------------------------
From: Pierre Schweitzer
Sent: 22-09-2013 PM 03:26
To: ros-dev(a)reactos.org
Subject: Re: [ros-dev] reactos.org is down
Hi,
we're currently getting back online.
Sorry for the inconvenience caused by this downtime.
With my best regards,
On 22/09/2013 11:25, Александр wrote:
reactos.org is down
--
С наилучшими пожеланиями, Александр.
_______________________________________________
Ros-dev mailing
listRos-dev@reactos.orghttp://www.reactos.org/mailman/listinfo/ros-dev
--
Pierre Schweitzer<pierre at reactos.org>
System Administrator
ReactOS Foundation
I think a call to IoReleaseCancelSpinLock should be balanced with a call to
IoAcquireCancelSpinLock somewhere in the npfs_new code, however, looking at:
http://git.reactos.org/?p=reactos.git
<http://git.reactos.org/?p=reactos.git&a=search&h=HEAD&st=grep&s=IoAcquireCa
ncelSpinLock> &a=search&h=HEAD&st=grep&s=IoAcquireCancelSpinLock
I dont see any call to IoAcquireCancelSpinLock in npfs_new. Can someone
explain to me, why ?
Hermès
Author: tfaber
Date: Fri Sep 20 06:49:21 2013
New Revision: 60231
URL: http://svn.reactos.org/svn/reactos?rev=60231&view=rev
Log:
[NPFS]
- Release cancel spinlock in NpCancelListeningQueueIrp
Modified:
trunk/reactos/drivers/filesystems/npfs_new/statesup.c
Modified: trunk/reactos/drivers/filesystems/npfs_new/statesup.c
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/filesystems/npfs_ne
w/statesup.c?rev=60231&r1=60230&r2=60231&view=diff
============================================================================
==
--- trunk/reactos/drivers/filesystems/npfs_new/statesup.c [iso-8859-1]
(original)
+++ trunk/reactos/drivers/filesystems/npfs_new/statesup.c [iso-8859-1] Fri
Sep 20 06:49:21 2013
@@ -20,6 +20,8 @@
NpCancelListeningQueueIrp(IN PDEVICE_OBJECT DeviceObject,
IN PIRP Irp)
{
+ IoReleaseCancelSpinLock(Irp->CancelIrql);
+
FsRtlEnterFileSystem();
NpAcquireExclusiveVcb();
On 2013-09-18 01:02, hbelusca(a)svn.reactos.org wrote:
> Added:
> branches/ntvdm/lib/soft386/common.inl (with props)
It's a header file. Can you name it .h please to not break syntax
highlight? Thanks.
Timo originally proposed this but I'd like to actually see the
proposal implemented. When working on ReactOS, I'd like developers to
create tickets in jira that their commits can then reference. For
example, Amine's wine syncs could have a ticket with the title "Wine
sync with version 1.x.y" or Alex's NPFS rewrite could have a ticket
with the title "New NPFS driver" and the relevant commits can have the
ticket number in them. This way when time comes for the changelog, all
that needs to be done is gather a list of all tickets closed before
the branch, no more of the digging through thousands of commit
messages crap.