<div dir="ltr">Hi,<br><br><div class="gmail_quote"><div dir="ltr">On Wed, Aug 1, 2018 at 2:41 PM Eric Irrgang <<a href="mailto:ericirrgang@gmail.com">ericirrgang@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> I'm sure there are ways to improve things here, and the more important<br>
> thing is to write words than worry about where to host them. Do note that<br>
> there are things in the developer guide in the source repo, which we should<br>
> not duplicate!<br>
<br>
Mark: I'm sorry, but your last comment is not clear to me, maybe<br>
because it goes to my original question.<br>
I don't imagine you are pointing out that we shouldn't duplicate the<br>
source repo. (Ah, the joys of English grammar...) Do you mean we<br>
should not propagate the fact that things in the developer guide are<br>
in the source repo? Or that if some piece of information is already in<br>
the source repo, that it should be referenced instead of duplicated?<br>
Also, I think the term "developer guide" is explicitly used only in<br>
the Sphinx sources in the repo (also "dev manual"), but I wanted to<br>
double-check that this is what you mean.<br></blockquote><div><br></div><div>I think it would be efficient not to spend time writing text that is similar to text we already have. e.g. we should perhaps move and update the existing section on uncrustify rather than write a fresh one. Or spend the time getting clang-format to work close enough to the existing style that we can retire uncrustify. Or adding the smarts to a Jenkins job to create a post-uncrustify patch that can be transferred to gerrit easily.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The gist, though, seems to be that I should submit a patch to Gerrit,<br>
and if the content is not appropriate to port, it will be addressed in<br>
code review. I was hoping to get specific thumbs up or down before<br>
spending time on formatting, but it isn't that big a deal, so I'll<br>
start a patch as soon as I figure out why the webpage isn't building<br>
for me with Sphinx 1.7.x<br></blockquote><div><br></div><div>There's probably stuff that doesn't make sense in the source repo, but it's what we have for now until someone has time to work on the new webpage.</div><div><br></div><div>Mark</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-- <br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" rel="noreferrer" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before posting!<br>
<br>
* Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" rel="noreferrer" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
* For (un)subscribe requests visit<br>
<a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" rel="noreferrer" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or send a mail to <a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.<br>
</blockquote></div></div>