This is fine. My confusion is from this: I didn't enable svn or hg in the very beginning, and started writing wiki... after a while, I enabled svn, then found my wiki cannot be edited - and after tried to add a new wiki item, old wiki is gone. That's what I'm upset about.
On Nov 11, 11:54 pm, Ben Collins-Sussman <[email protected]> wrote: > If you switch your project from svn to hg, then the svn repository > (which contains code AND wiki pages) is still available and read-only. > No data is lost. The code and wiki pages can still be checked-out. > > If you 'reset' your svn repository, then all of the code and wiki > pages are deleted together: it's all one repository, and it's all > destroyed. > > Does this make sense? > > > > On Wed, Nov 11, 2009 at 5:03 AM, Fu Yicong <[email protected]> wrote: > > > For #2: in that case, that would be appreciated: at least my code is > > not lost. > > But, if code changes to read-only, why wiki cannot? At least it had > > better let me copy out the wiki content which is full of markup. > > > On Nov 11, 11:06 am, Ben Collins-Sussman <[email protected]> wrote: > >> I think you're mixing up two separate problems here: > > >> 1. Resetting a repository deletes not only the repository contents, > >> but the wiki too. There's a problem in that not everybody realizes > >> the wiki is stored in the /wiki directory of subversion. We need to > >> remind people of that before they obliterate their own svn data. > > >> 2. Switching from svn to hg entails *no* risk at all. The svn > >> repository is still available after the switch; it's simply > >> read-only. Thus it's easy to still 'svnsync' the svn history (the > >> export function you hypothesize about) to elsewhere, or 'hg convert' > >> the svn repository into a new hg repository. > > >> On Tue, Nov 10, 2009 at 8:33 PM, Fu Yicong <[email protected]> wrote: > > >> > Thanks Chris and Ben for the reply. > >> > If it is costly to support the seamless data migration, then it is a > >> > MUST to prompt an explicit warning when user turns on or switches > >> > version control. Otherwise, the switch could be comprehended as > >> > ordinary as changing a preference item, while in fact it is not - on > >> > the contrary, a disastrous action. > > >> > Besides, is it possible to provide a data export function? If version > >> > control switch is inevitable, user at least should be able to download > >> > all his/her wiki/source code to local, then upload again after version > >> > control switch is done. (or, can you put a notice as a good practice: > >> > "Before switching, please clone all the data from repository to local > >> > as primary data, ....." Instructing user what to do to help migrating > >> > his/her data is always considerate) > > >> > On Nov 10, 10:33 am, Ben Collins-Sussman <[email protected]> wrote: > >> >> We are definitely planning to add a note that you suggest, Chris... so > >> >> that people resetting their repositories are reminded that the wiki is > >> >> stored there too. > > >> >> Also: in the case of dire mistakes and hundreds of hours of lost wiki > >> >> data, we can also restore wiki stuff from backup. It would have to be > >> >> a special case, but it's possible. > > >> >> On Mon, Nov 9, 2009 at 7:28 PM, Chris DiBona <[email protected]> wrote: > >> >> > When a user resets their version control, where those wiki pages were > >> >> > stored, and then they were no longer available, this is the > >> >> > programmed behavior. This isn't an ambiguous result. > >> >> > I might point out that the reset routine says in big red letters, > >> >> > Warning: Resetting the repository will delete everything in the > >> >> > repository > >> >> > and its history. > >> >> > Additionally, it asks you to consider mightily what you are doing. I > >> >> > don't > >> >> > think that we can do more than we're doing while maintaining > >> >> > functionality > >> >> > and have it change the number of people who overlook this and make a > >> >> > mistake > >> >> > while resetting. > >> >> > I have sympathy, as I've made similar mistakes, one answer might be > >> >> > that we > >> >> > might want to add "Including any wiki content you may have made", but > >> >> > the > >> >> > rest is pretty clear that this is a fairly dire thing to want to do. > >> >> > Chris > > >> >> > On Mon, Nov 9, 2009 at 5:14 PM, Fu Yicong <[email protected]> wrote: > > >> >> >> My god, how can this happen?? After I found that my old wiki contents > >> >> >> are not editable, I tried to create a new one, then found that all my > >> >> >> old contents are gone!! > >> >> >> Such unexpected data loss should never be overlooked by > >> >> >> code.google.com engineers, right?? It's lucky that I happened to have > >> >> >> a quick backup - copy+paste to a rich editor, but later turned out > >> >> >> just ill-formatted text afterwards..... > > >> >> >> Since many project owners like me, may have written wiki by hand > >> >> >> first, without using any SCM, later decided to turn on svn or hg, do > >> >> >> you expect they to see losing existing wiki at all?? > >> >> >> Even you may put a warning, it still require extra work for project > >> >> >> owners to transit old wiki to new one - and is there a good way? - > >> >> >> Just how difficult is it to migrate old wiki to new one seamlessly > >> >> >> and > >> >> >> automatically? Must there be a suffering for end users? > > >> >> >> I'm already losing quite some trust in code.google.com. Starting to > >> >> >> wonder what if I happen to switch from svn to hg one day, will it > >> >> >> lose > >> >> >> data too? Both code and document? Can't imagine. > > >> >> >> Hope anyone who's in charge provide an answer to we faithful but > >> >> >> disappointed Google users. > > >> >> >> On Nov 7, 5:34 am, Jacob Lee <[email protected]> wrote: > >> >> >> > That's occurring because your wiki pages no longer exist in source > >> >> >> > control. Wiki pages are stored under /wiki in your subversion > >> >> >> > repository; when you reset the repository, you deleted those wiki > >> >> >> > pages. Unfortunately, the wiki editor doesn't handle this case > >> >> >> > well at > >> >> >> > all - it throws errors. > > >> >> >> > If you want, we can synchronize your wiki with the contents in > >> >> >> > subversion - just note that in your case, this will remove all of > >> >> >> > your > >> >> >> > wiki pages. > > >> >> >> > -- > >> >> >> > Jacob Lee > >> >> >> > [email protected] > > >> >> >> > On Fri, Nov 6, 2009 at 4:15 PM, Kevin <[email protected]> wrote: > > >> >> >> > > when trying to edit any of my wiki pages, i get the following > >> >> >> > > error > > >> >> >> > > Server Error > > >> >> >> > > The server encountered an error and could not complete your > >> >> >> > > request. > >> >> >> > > If the problem persists, please report your problem and mention > >> >> >> > > this > >> >> >> > > error message and the query that caused it. > > >> >> >> > > The report link takes me to the main google help, where google > >> >> >> > > code is > >> >> >> > > no where to be found. > > >> >> >> > > What do i do? > > >> >> > -- > >> >> > Open Source Programs Manager, Google Inc. > >> >> > Google's Open Source and Developer programs can be found at > >> >> >http://code.google.com > >> >> > Personal Site and Weblog:http://dibona.com -- You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=.
