{"thread":{"id":"32479","subject":"Aw: Re: [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical","startedAt":"2012-12-30T14:56:33Z","lastAt":"2012-12-31T09:33:51Z","messageCount":3,"participants":["Thomas Ackermann","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":3},"messages":[{"id":"205677","messageId":"1965427282.405137.1356879393533.JavaMail.ngmail@webmail18.arcor-online.net","threadId":"32479","inReplyTo":null,"subject":"Aw: Re: [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical","fromName":"Thomas Ackermann","fromEmail":"th.acker@arcor.de","sentAt":"2012-12-30T14:56:33Z","receivedAt":"2012-12-30T14:56:33Z","isPatch":true,"sender":{"key":"th.acker@arcor.de","avatar":"https://avatars.githubusercontent.com/u/1358536?v=4"},"body":" \n./Documentation/technical contains not only API documentation but also\nseveral other documents describing Git implementation topics and thus\nis the place someone wanting to join Git development should look at.\nSo IMHO CodingGuidelines and SubmittingPatches should also be there.\n(One could even consider renaming ./technical to ./internal to stress this point\nand get rid of the rather generic \"technical\" ...)\n\nIn contrast ./howto implies containing documents a Git *user* might \nneed to solve some tricky problems (and to this end maintain-git.txt\nand new-command.txt should also be moved to ./technical (sorry for\nbeing the guy who just moved ./technical/api-command to \n./howto/new-command.txt ;-)).\n\n./Documentation itself should only contain the command manpages\nand tutorials.\n\n----- Original Nachricht ----\nVon:     Ramkumar Ramachandra <artagnon@gmail.com>\nAn:      Thomas Ackermann <th.acker@arcor.de>\nDatum:   30.12.2012 12:52\nBetreff: Re: [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical\n\n> Thomas Ackermann wrote:\n> > CodingGuidelines and SubmittingPatches are IMHO a little bit hidden in\n> ./Documentation\n> > and with respect to their content should be better placed in\n> ./Documentation/technical.\n> \n> I don't think SubmittingPatches and CodingGuidelines belong to\n> Documentation/technical; that location is mostly reserved for API\n> documentation.  Also, being prominent documents, they're probably\n> linked to by many places on the internet.  I wouldn't want to\n> unnecessarily break those links.\n> \n> Ram\n> \n\n---\nThomas\n"},{"id":"205687","messageId":"7v1ue7fcbh.fsf@alter.siamese.dyndns.org","threadId":"32479","inReplyTo":"1965427282.405137.1356879393533.JavaMail.ngmail@webmail18.arcor-online.net","subject":"Re: Aw: Re: [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-12-30T21:40:50Z","receivedAt":"2012-12-30T21:40:50Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thomas Ackermann <th.acker@arcor.de> writes:\n\n>  \n> ./Documentation/technical contains not only API documentation but also\n> several other documents describing Git implementation topics and thus\n> is the place someone wanting to join Git development should look at.\n\nImplementation details are part of API; CG and SP are social not\ntechnical.\n\nAlso CG and SP are in the part of the documents that are not\ninstalled for end-users and that is their right place.  They matter\nonly to the people who grab our source code.\n"},{"id":"205692","messageId":"2010399637.417873.1356946431500.JavaMail.ngmail@webmail08.arcor-online.net","threadId":"32479","inReplyTo":"7v1ue7fcbh.fsf@alter.siamese.dyndns.org","subject":"Aw: Re: Aw: Re: [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical","fromName":"Thomas Ackermann","fromEmail":"th.acker@arcor.de","sentAt":"2012-12-31T09:33:51Z","receivedAt":"2012-12-31T09:33:51Z","isPatch":true,"sender":{"key":"th.acker@arcor.de","avatar":"https://avatars.githubusercontent.com/u/1358536?v=4"},"body":" \n> \n> Implementation details are part of API; CG and SP are social not\n> technical.\n> \nThis depends on your definition of \"social\" ;-)\n> \n> Also CG and SP are in the part of the documents that are not\n> installed for end-users and that is their right place.  They matter\n> only to the people who grab our source code.\n> \nBut isn't that true for all files in ./technical? CG and SP currently\nare in ./Documentation which contains *only* files which are installed\nfor end-users with CG and SP the only exception ...\n\n\n---\nThomas\n"}]}