Wed, Aug 29, 2012 16:09, André Hentschel wrote:
get the website source and do "grep -Ri cvs *" then ignore wwn/ and news/
...
all that should somehow bring you to http://www.winehq.org/cvs or be deleted
grep -r "...." * is rapidly becoming a very good friend of mine ;) I just checked http://cvs.winehq.org and sure enough, there is still a very outdated CVS repository there, but I can't find a template or a PHP applet for it, just the same links you found (most in WWN issues). I've CCed Jeremy Newman because I'm guessing the site admin would have to remove it.
As for redirecting to http://www.winehq.org/cvs, since that was designed as a notice page for people trying to browse the source code, I was picturing just redirecting the links to http://source.winehq.org/git and deleting http://www.winehq.org/cvs as only WWN issues and news would still have dangling links. I don't want to remove it if there's another reason for keeping it though.
- Kyle
On 08/29/2012 09:32 PM, Kyle Auble wrote:
just checked http://cvs.winehq.org and sure enough, there is still a very outdated CVS repository there, but I can't find a template or a PHP applet for it, just the same links you found (most in WWN issues). I've CCed Jeremy Newman because I'm guessing the site admin would have to remove it.
I am not opposed to removing it. We had left it up as a historical archive, or for people that were not ready to switch to GIT yet. If there is consensus then I can certainly take it down.
On 08/30/2012 06:05 PM, Jeremy Newman wrote:
On 08/29/2012 09:32 PM, Kyle Auble wrote:
just checked http://cvs.winehq.org and sure enough, there is still a very outdated CVS repository there, but I can't find a template or a PHP applet for it, just the same links you found (most in WWN issues). I've CCed Jeremy Newman because I'm guessing the site admin would have to remove it.
I am not opposed to removing it. We had left it up as a historical archive, or for people that were not ready to switch to GIT yet. If there is consensus then I can certainly take it down.
According to Alexandre it is used by http://source.winehq.org/ for the "Wine Cross Reference".
bye michael
Thu, Aug 30, 2012 12:23, Michael Stefaniuc wrote:
On 08/30/2012 06:05 PM, Jeremy Newman wrote:
On 08/29/2012 09:32 PM, Kyle Auble wrote:
just checked http://cvs.winehq.org and sure enough, there is still a very outdated CVS repository there, but I can't find a template or a PHP applet for it, just the same links you found (most in WWN issues). I've CCed Jeremy Newman because I'm guessing the site admin would have to remove it.
I am not opposed to removing it. We had left it up as a historical archive, or for people that were not ready to switch to GIT yet. If there is consensus then I can certainly take it down.
According to Alexandre it is used by http://source.winehq.org/ for the "Wine Cross Reference".
Ahhh, that certainly changes things. Does the server have to run a CVS instance to generate the web interface? If so, and if it's possible to somehow store the CVS data somewhere else, it might not hurt to consolidate it someday. That's really distant, low-priority stuff though. I'll remove the line from the WineHQ Todo list and make a note on the wiki SourceCode page so no one gets confused.
- Kyle
Michael Stefaniuc mstefani@redhat.com writes:
On 08/30/2012 06:05 PM, Jeremy Newman wrote:
On 08/29/2012 09:32 PM, Kyle Auble wrote:
just checked http://cvs.winehq.org and sure enough, there is still a very outdated CVS repository there, but I can't find a template or a PHP applet for it, just the same links you found (most in WWN issues). I've CCed Jeremy Newman because I'm guessing the site admin would have to remove it.
I am not opposed to removing it. We had left it up as a historical archive, or for people that were not ready to switch to GIT yet. If there is consensus then I can certainly take it down.
According to Alexandre it is used by http://source.winehq.org/ for the "Wine Cross Reference".
Actually that doesn't use CVS, it's using a static copy. It should really use git instead, but that's a different issue.
Am 30.08.2012 04:32, schrieb Kyle Auble:
As for redirecting to http://www.winehq.org/cvs, since that was designed as a notice page for people trying to browse the source code, I was picturing just redirecting the links to http://source.winehq.org/git and deleting http://www.winehq.org/cvs as only WWN issues and news would still have dangling links. I don't want to remove it if there's another reason for keeping it though.
please don't remove it. there's still much linking to it on the web, or hiding links, like in sourcecodes somewhere
Thu, Aug 30, 2012 11:55, André Hentschel wrote:
Am 30.08.2012 04:32, schrieb Kyle Auble:
As for redirecting to http://www.winehq.org/cvs, since that was designed as a notice page for people trying to browse the source code, I was picturing just redirecting the links to http://source.winehq.org/git and deleting http://www.winehq.org/cvs as only WWN issues and news would still have dangling links. I don't want to remove it if there's another reason for keeping it though.
please don't remove it. there's still much linking to it on the web, or hiding links, like in sourcecodes somewhere
OK, sounds good. I'll leave the CVS notice pages but update the links.
- Kyle
-
Alexandre Julliard -
André Hentschel -
Jeremy Newman -
Kyle Auble -
Michael Stefaniuc