Migrating BerliOS to SourceForge

[Alpha]

All pages on http://alpha0010.github.io/cb-history/ are now populated (lots of issues scraping together the features page because the dump from BerliOS contains none of that data) with all history I was able to get access to.  Links within the comments that direct to BeriOS are (for the most part) rewritten to link internally.

Here is another idea: once a bug is fixed in our trunk, can the bug web page be marked as closed or fixed. I mean if it can have futures(API) that devs have rights to edit the issue item.

Hmm, this would be difficult to do live because hosting webpages on github restricts you to serving only static content.  I could grant devs commit access to the repo.  Or, I could regenerate the pages if someone lets me know whenever a ticket is closed.

[ollydbg]

Hi, Alpha, with you page and Google, I can quick find and locate an old bug(see: Re: Patch for inserting implementation), thanks.

Here is a small bug.
Look at the page: http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html, the first comments still contains a link which jump to berlios.

Here is another idea: once a bug is fixed in our trunk, can the bug web page be marked as closed or fixed. I mean if it can have futures(API) that devs have rights to edit the issue item.

Hmm, this would be difficult to do live because hosting webpages on github restricts you to serving only static content.  I could grant devs commit access to the repo.  Or, I could regenerate the pages if someone lets me know whenever a ticket is closed.

Fine, thanks.

[ollydbg]

Another two issue:
1, The web link format is currently

Code Select Expand

http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html
Is it possible to change to some thing like:

Code Select Expand

http://alpha0010.github.io/cb-history/bugs/18526.html which is much cleaner.

2, Is comments in the same thread sorted? In the page: http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html
I see that a newer comment is put in the first.

Still these can be feature request, thanks.

[Alpha]

Look at the page: http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html, the first comments still contains a link which jump to berlios.

Odd... I must have messed up my regex's or something; looking into it.

1, The web link format is currently

Code Select Expand

http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html
Is it possible to change to some thing like:

Code Select Expand

http://alpha0010.github.io/cb-history/bugs/18526.html which is much cleaner.

I could change it, but I personally prefer having some detail in the file name.  That way, it is easier to identify files on disk (especially if you are downloading multiple patch files).  What do you think?  Maybe simplify the .html, but leave the .patch file names?

2, Is comments in the same thread sorted? In the page: http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html
I see that a newer comment is put in the first.

They are supposed to be sorted.  Reviewing my code, it appears some them get sorted, and some of them just (incorrectly) assume they are already sorted.

[ollydbg]

1, The web link format is currently

Code Select Expand

http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html
Is it possible to change to some thing like:

Code Select Expand

http://alpha0010.github.io/cb-history/bugs/18526.html which is much cleaner.

I could change it, but I personally prefer having some detail in the file name.  That way, it is easier to identify files on disk (especially if you are downloading multiple patch files).  What do you think?  Maybe simplify the .html, but leave the .patch file names?

Hi, thanks.
The reason I would like to see a short html is that some times, I may add this link to our SVN commit message, such as:

Code Select Expand


* CC: fix a bug xxxx, see: http://alpha0010.github.io/cb-history/bugs/18526.html

So, we can have a clean web page reference. I don't have much strong option whether option is good. 

About the patch names, I totally agree with you, the patch name should have some details in the file name. 

[Alpha]

Pages renamed and comments sorted.

[ollydbg]

Pages renamed and comments sorted.

Great work, thanks!

[Alpha]

The pages all have basic filtering controls, so now it is a bit more manageable to navigate.  If anyone has a request for another field I implement filtering on, let me know (although, I would prefer to keep filters down to only the most useful ones).