Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
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.
--- Quote from: ollydbg on June 12, 2014, 05:49:38 am ---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.
--- End quote ---
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.
--- Quote from: Alpha on June 15, 2014, 04:14:02 am ---
--- Quote from: ollydbg on June 12, 2014, 05:49:38 am ---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.
--- End quote ---
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.
--- End quote ---
Fine, thanks.
ollydbg:
Another two issue:
1, The web link format is currently
--- Code: ---http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html
--- End code ---
Is it possible to change to some thing like:
--- Code: ---http://alpha0010.github.io/cb-history/bugs/18526.html
--- End code ---
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:
--- Quote from: ollydbg on June 18, 2014, 08:28:17 am ---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.
--- End quote ---
Odd... I must have messed up my regex's or something; looking into it.
--- Quote from: ollydbg on June 18, 2014, 10:08:00 am ---1, The web link format is currently
--- Code: ---http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html
--- End code ---
Is it possible to change to some thing like:
--- Code: ---http://alpha0010.github.io/cb-history/bugs/18526.html
--- End code ---
which is much cleaner.
--- End quote ---
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?
--- Quote from: ollydbg on June 18, 2014, 10:08:00 am ---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.
--- End quote ---
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:
--- Quote from: Alpha on June 20, 2014, 12:31:18 am ---
--- Quote from: ollydbg on June 18, 2014, 10:08:00 am ---1, The web link format is currently
--- Code: ---http://alpha0010.github.io/cb-history/bugs/18526-Insert_all_cl.html
--- End code ---
Is it possible to change to some thing like:
--- Code: ---http://alpha0010.github.io/cb-history/bugs/18526.html
--- End code ---
which is much cleaner.
--- End quote ---
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?
--- End quote ---
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: ---* CC: fix a bug xxxx, see: http://alpha0010.github.io/cb-history/bugs/18526.html
--- End code ---
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. :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version