On Thu, Jan 22, 2009 at 7:11 PM, Frank Sweetser <[email protected]> wrote:
> John Drescher wrote:
>> On Thu, Jan 22, 2009 at 7:06 PM, Frank Sweetser <[email protected]> wrote:
>>> Dan Langille wrote:
>>>> On Jan 22, 2009, at 6:54 PM, Kern Sibbald wrote:
>>>>
>>>>> On Thursday 22 January 2009 23:59:26 Dan Langille wrote:
>>>>>> This sounds clever.  Hard to do?
>>>>>>
>>>>> No, it is essentially the same a item 24 in the projects file.
>>>>> since it was
>>>>> 24 on the last vote, given the items above it, unfortunately we are
>>>>> unlikely
>>>>> to get to it any time soon, even though many of the items above it
>>>>> have
>>>>> already been completed for version 3.0.0
>>>> Is that the right number?  24?
>>>>
>>>> http://www.bacula.org/en/?page=projects
>>>>
>>>> Item 24:  Add an override in Schedule for Pools based on backup types.
>>> It looks like it's item 24 on the latest projects file:
>>>
>>> http://bacula.svn.sourceforge.net/viewvc/bacula/trunk/bacula/projects?view=markup
>>>
>>> Perhaps the projects link on the main page should be updated to point to 
>>> this
>>> version instead?
>>>
>>
>> Its 15 there:
>>
>> Item:  15   Multiple threads in file daemon for the same job
>>
>> John
>
> Strange, I see
>
> Item 15:  Implement more Python events and functions  --- Abandoned for 
> plugins
>
> and
>
> Item 24:  Multiple threads in file daemon for the same job
>
> What revision does that page show you?  And if it's anything other than 8084,
> does this link show you the correct file?
>
> http://bacula.svn.sourceforge.net/viewvc/bacula/trunk/bacula/projects?revision=HEAD&view=markup
>
I meant 15 on the main page:

http://www.bacula.org/en/?page=projects

John

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to