[prev in list] [next in list] [prev in thread] [next in thread] 

List:       horde-dev
Subject:    Re: [dev] [Tickets #2245] RESOLVED: Horde Share implementation for
From:       Michael Rubinsky <mike () theupstairsroom ! com>
Date:       2005-08-26 20:56:09
Message-ID: 20050826165609.dcxdgwbn5ugc8sck () theupstairsroom ! dynip ! com
[Download RAW message or body]

Sorry Chuck,
I'll be more careful with my vocabulary.  I checked through the sources 
to make sure I didn't refer to it like that in any comments etc...looks 
clean.

Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk@horde.org


Quoting bugs@coyote.horde.org:

> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
>
> Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=2245
> -----------------------------------------------------------------------
> Ticket             | 2245
> Updated By         | Chuck Hagenbuch <chuck@horde.org>
> Summary            | Horde Share implementation for Turba
> Queue              | Turba
> Version            | HEAD
> State              | Resolved
> Priority           | 1. Low
> Type               | Enhancement
> Owners             | Michael Rubinsky
> -----------------------------------------------------------------------
>
>
> Chuck Hagenbuch <chuck@horde.org> (2005-08-26 06:53) wrote:
>
>> Right now the only backend supporting shares is localsql
>
> No, it's sql. You make me really nervous every time you refer to localsql as
> if it was something other than the default name for a source in an example
> configuration file. It should *not* be more.
>
>


-- 
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@lists.horde.org
[prev in list] [next in list] [prev in thread] [next in thread]