digitalmars.D - d-p-l.org statement.html
- Johann MacDonagh (3/3) Jul 13 2011 http://www.d-programming-language.org/statement.html
- Jonathan M Davis (9/13) Jul 13 2011 Easily. When it gives you a merge conflict, you just commit the file gen...
- Johann MacDonagh (6/13) Jul 16 2011 I know, but usually git is keeping track of a merge and won't let a file...
- Loopback (12/12) Jul 14 2011 While speaking of the website, how come
- Trass3r (1/4) Jul 14 2011 Yep, that's broken too.
- Jonathan M Davis (5/19) Jul 14 2011 Please report issues with the website at d.puremagic.com/issues
- Johann MacDonagh (1/2) Jul 16 2011 Done. http://d.puremagic.com/issues/show_bug.cgi?id=6335
- Trass3r (7/7) Jul 15 2011 Also at http://www.d-programming-language.org/phobos/std_getopt.html
http://www.d-programming-language.org/statement.html Scroll down to the bottom. Looks like someone committed a file that had merge markup in it. I'm not even sure how git would let you do this.
Jul 13 2011
On Wednesday 13 July 2011 21:49:00 wrote:http://www.d-programming-language.org/statement.html Scroll down to the bottom. Looks like someone committed a file that had merge markup in it. I'm not even sure how git would let you do this.Easily. When it gives you a merge conflict, you just commit the file generated from the merge without dealing with the conflicts - or you do try and deal with the conflicts but you miss one. That sort of thing is caught very easily with code, because it's not going to compile with all of those >>>>>>>>>> and <<<<<<< in the file. ddoc, on the other hand, can legally contain >>>>>>> and <<<<<<<, so the documentation compiled just fine. No one caught it, and it ended up in the master repository. - Jonathan M Davis
Jul 13 2011
Easily. When it gives you a merge conflict, you just commit the file generated from the merge without dealing with the conflicts - or you do try and deal with the conflicts but you miss one. That sort of thing is caught very easily with code, because it's not going to compile with all of those>>>>>>>>>> and <<<<<<< in the file. ddoc, on the other hand, can legally contain>>>>>>> and <<<<<<<, so the documentation compiled just fine. No one caught it, and it ended up in the master repository.I know, but usually git is keeping track of a merge and won't let a file with merge markup be committed unless you specifically force it. If you go through the normal merge conflict resolution process all of that should be removed. Anyway, it doesn't look like the markup got committed, I think it was just generated from a file that hadn't been resolved yet.
Jul 16 2011
While speaking of the website, how come "http://d-programming-language.org/language_reference.html" just redirects one instantly to the lexical section? language-reference.html <html> <head> <title>D Runtime Library</title> <meta http-equiv="Refresh" content="0; URL=lex.html"> </head> <body> </body> </html>
Jul 14 2011
While speaking of the website, how come "http://d-programming-language.org/language_reference.html" just redirects one instantly to the lexical section?Yep, that's broken too.
Jul 14 2011
On 2011-07-14 12:12, Loopback wrote:While speaking of the website, how come "http://d-programming-language.org/language_reference.html" just redirects one instantly to the lexical section? language-reference.html <html> <head> <title>D Runtime Library</title> <meta http-equiv="Refresh" content="0; URL=lex.html"> </head> <body> </body> </html>Please report issues with the website at d.puremagic.com/issues When creating the bug, choose D (not DStress or puremagic.com) and select the websites component. - Jonathan M Davis
Jul 14 2011
Please report issues with the website at d.puremagic.com/issuesDone. http://d.puremagic.com/issues/show_bug.cgi?id=6335
Jul 16 2011
Also at http://www.d-programming-language.org/phobos/std_getopt.html I get Depending on the type of the pointer being bound, getopt recognizes the following kinds of options: (OL // <--- Boolean options. These are the simplest options; all they do is set a Boolean to true:
Jul 15 2011