Alex,
Your project interests me, since I have still not invested my time in
installing the 'current' server and I'm still looking for a replacement for
the manual execution of unprivileged up2date.
OTOH, I'm not a 'current' developer. Maybe they are all on vacation, or
maybe the interest is limited. I don't know.
I'm a curious 'lurker' on this list, trying to understand what 'current'
could benefit us in my local network and I will study your solution before
deciding what we will start using.
Cheers
Gustav
|--------+----------------------------------------->
| | "Alex Kramarov" |
| | <[email protected]> |
| | Sent by: |
| | [email protected]|
| | g.duke.edu |
| | |
| | |
| | 13-08-02 02:29 PM |
| | Please respond to |
| | current-server |
| | |
|--------+----------------------------------------->
>--------------------------------------------------------------------------------------------------|
| |
| To: <[email protected]> |
| cc: (bcc: Gustav Schaffter/CDS/CG/CAPITAL) |
| Subject: Re: [Current-server] another approach to what current does |
>--------------------------------------------------------------------------------------------------|
SHIT. It was down for the last 12 hours or so, judging from the apache log.
By the way, this is the only response i got to my emails. My intention is
not to compete with your product, but to introduce another one, in a
somewhat different scale, that will respond to population other then your
target population. I simply would like to talk to one of the developers to
see if we can work together - I don't think that this can be considered a
waste of time, because my project is a valid, working idea.
Alex.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.