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

List:       kde-bugs-dist
Subject:    [Bug 142196] ooosvn for revision control
From:       Sebastian Sauer <mail () dipe ! org>
Date:       2007-02-28 3:02:34
Message-ID: 20070228030234.9379.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=142196         
mail dipe org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From mail dipe org  2007-02-28 04:02 -------
So, let's mark this wish as WONTFIX for now since the current OOoSVN-implementation just looks \
like OOo-only. If anybody does not agree there, please feel free to reopen the wish + provide \
some more details why I am wrong with my opinion. If it's all about getting a "joint effort" \
established to provide a solution other Office-suites like KOffice are able to use, then I \
would suggest to start first to define how such a solution needs to look like (e.g. what \
language, how to let apps access the functionality, maybe implement a lib? and what is the \
advantage compared to use the libsvn direct - e.g. provide support for more backends then only \
subversion? etc.). So, as sayed, I absolut like the idea to have here a solution that could be \
used by much more apps and it's a very good idea! I just don't see how it could be done with \
the current implementation :-(


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