<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">That’s interesting because when I was doing my checkins to test my access, I was doing them in the “bob” branch, so they should have just stayed there. I didn’t use the process that I described on the trunk. Weird. <div><br></div><div>I was thinking that the development process that I was describing was taking place in a branch, but from what you say we don’t need to be that careful there. </div><div><br></div><div>So is the following what you’re talking about for development?</div><div><br></div><div>+ Make branch (e.g. bob_dev)</div><div> - including branch versions of external repositories</div><div><br></div><div>+ Checkout branch</div><div><br></div><div>+ In branch edit externals to point to trunks of branch versions of externals</div><div><br></div><div>+ Do I then need to commit this and recheck out my branch??</div><div><br></div><div>+ Edit files</div><div><br></div><div>+ Commit these (they’ll go to the branch)</div><div><br></div><div>+ When I’m happy with the changes, have my friendly neighborhood code manager merge the changes from my branch to the trunk</div><div> As part of this they will: </div><div> - modify the trunk externals to point to the updated versions of the repositories</div><div> - update the test baselines to reflect the most recent results</div><div><br></div><div><br></div><div>Sorry to be so pesky about this, but I want to make sure that I’m doing what you intend with the branches and externals.</div><div><br></div><div>Thanks for your help.</div><div><br></div><div>- Bob</div><div><div><br></div><div><br><div><div>On May 19, 2017, at 11:22 AM, Samuel Trahan - NOAA Affiliate <<a href="mailto:samuel.trahan@noaa.gov">samuel.trahan@noaa.gov</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div>Bob,<br><br></div>No. You should work in a branch, and your working (disk) copy should be a checkout of your branch. If you followed the process you described, then you probably committed local changes to the svn:externals. If you work in a branch instead, you can change externals all you want without accidentally changing the trunk. <br><br></div>Sincerely,<br></div>Sam Trahan<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 19, 2017 at 1:17 PM, Robert Oehmke <span dir="ltr"><<a href="mailto:robert.oehmke@noaa.gov" target="_blank">robert.oehmke@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Sure. That makes sense. The thing that I’m unclear on is the details of the development process. When we check out WAM-IPE we’ll be at specific revisions, so we’re not modifying the trunk. <div><br></div><div>For development do we do something like this: </div><div><br></div><div>+ Update the repository that we’re editing to the trunk version</div><div> - cd into the repository directory</div><div> - do svn update to bring the local version up to the trunk</div><div><br></div><div>+ Make changes to files</div><div><br></div><div>+ Check in changes</div><div> - do svn commit</div><div><br></div><div>+ Change externals to point to latest revision of that repository</div><div><br></div><div>Is that the process? </div><div><br></div><div>Thanks,</div><div><br></div><div>- Bob</div><div><div class="h5"><div><br></div><div><div><br></div><div> <br><div><div>On May 19, 2017, at 10:59 AM, Samuel Trahan - NOAA Affiliate <<a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a>> wrote:</div><br class="m_-2554627419769191044Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div>Bob,<br><br></div>The externals for the trunk should always point to a revision in a Subversion repository or a tag in a git repository. This ensures you know exactly what version of each component is in use. That means you can make branches or tags of the trunk without having to manually make branches and tags of each component. It also makes execution easier for the trunk- you can run a particular version of the trunk against a particular version of the compset input/output data.<br><br></div>Sincerely,<br></div>Sam Trahan<br><div><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 19, 2017 at 12:04 PM, Robert Oehmke <span dir="ltr"><<a href="mailto:robert.oehmke@noaa.gov" target="_blank">robert.oehmke@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Sam,<div><br></div><div> Ok, I’ll give this a try. I guess that I’ll point it to the last version since all the changes from 91075 to then seen neutral. Could we just point to the trunk version of everything? Or is the idea to have some fixed version of all the repositories? If we want to edit something do we switch to the most recent version to go forward with? </div><div><br></div><div>Thanks,</div><div><br></div><div>- Bob</div><div><div class="m_-2554627419769191044h5"><br><div><div>On May 19, 2017, at 9:44 AM, Samuel Trahan - NOAA Affiliate <<a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a>> wrote:</div><br class="m_-2554627419769191044m_5731431828596589077Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div>Hi,<br><br></div>To correct the problem:<br><br></div>svn propedit svn:externals <a href="https://svnemc.ncep.noaa.gov/projects/nems/apps/WAM-IPE/trunk" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/apps/WAM-IPE/trun<wbr>k</a><br><br></div>Then change this line:<br><br> NEMS -r90130 <a href="https://svnemc.ncep.noaa.gov/projects/nems/branches/WAM-IPE/bob" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/branches/WAM-IPE/<wbr>bob</a><br><br></div>to point to a revision of the "quasitrunk" branch of NEMS:<br><br></div>NEMS -r??? <a href="https://svnemc.ncep.noaa.gov/projects/nems/branches/WAM-IPE/quasitrunk" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/branches/WAM-IPE/<wbr>quasitrunk</a><br><br></div>Replace ??? with the correct revision. Then save the file and exit your editor. An editor will be opened again so you can add a "commit message." Add a message and exit, then it will commit for you.<br><br><br>I'm not sure what revision (-r???) is the correct one. The top of the branch is revision 92673. Bob committed a change, "update mediator to be the same as milestone 0.5," on April 10. After that, the changes have been access tests. (See below.)<br><br>svn log <a href="https://svnemc.ncep.noaa.gov/projects/nems/branches/WAM-IPE/quasitrunk%7Chead" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/branches/WAM-IPE/<wbr>quasitrunk|head</a> -20<br>------------------------------<wbr>------------------------------<wbr>------------<br>r92673 | <a href="mailto:raffaele.montuoro@noaa.gov" target="_blank">raffaele.montuoro@noaa.gov</a> | 2017-05-12 17:16:13 +0000 (Fri, 12 May 2017) | 1 line<br><br>revert changes from previous test commit<br>------------------------------<wbr>------------------------------<wbr>------------<br>r92666 | <a href="mailto:raffaele.montuoro@noaa.gov" target="_blank">raffaele.montuoro@noaa.gov</a> | 2017-05-12 17:02:15 +0000 (Fri, 12 May 2017) | 1 line<br><br>test commit<br>------------------------------<wbr>------------------------------<wbr>------------<br>r92611 | <a href="mailto:robert.oehmke@noaa.gov" target="_blank">robert.oehmke@noaa.gov</a> | 2017-05-10 22:48:57 +0000 (Wed, 10 May 2017) | 1 line<br><br>test access<br>------------------------------<wbr>------------------------------<wbr>------------<br>r91075 | <a href="mailto:robert.oehmke@noaa.gov" target="_blank">robert.oehmke@noaa.gov</a> | 2017-04-10 19:31:20 +0000 (Mon, 10 Apr 2017) | 1 line<br><br>Update mediator to be the same as milestone 0.5<br>------------------------------<wbr>------------------------------<wbr>------------<br>r90318 | <a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a> | 2017-03-28 14:48:32 +0000 (Tue, 28 Mar 2017) | 1 line<br><br>delete test directory<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 19, 2017 at 10:56 AM, weiyu yang <span dir="ltr"><<a href="mailto:weiyu.yang@noaa.gov" target="_blank">weiyu.yang@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div class="m_-2554627419769191044m_5731431828596589077m_2973268618336821312moz-cite-prefix">I have a suggestion that the WAM-IPE
trunk should have only basic necessary external link, such as GSM,
IPE, etc. Everyone's personal branch should not be linked to the
WAM-IPE trunk. They may copy whole trunk as their personal branch
and work on it.<span class="m_-2554627419769191044m_5731431828596589077HOEnZb"><font color="#888888"><br>
Weiyu</font></span><div><div class="m_-2554627419769191044m_5731431828596589077h5"><br>
<br>
On 5/19/2017 8:36 AM, Samuel Trahan - NOAA Affiliate wrote:<br>
</div></div></div><div><div class="m_-2554627419769191044m_5731431828596589077h5">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>Bob,<br>
<br>
</div>
Yes, but make sure you point to the correct revision of the
quasitrunk<br>
<br>
</div>
Sincerely,<br>
</div>
Sam Trahan<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, May 18, 2017 at 5:45 PM, Robert
Oehmke <span dir="ltr"><<a href="mailto:robert.oehmke@noaa.gov" target="_blank">robert.oehmke@noaa.gov</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div><br>
</div>
<div>Yep, that’s true, maybe it happened when I was
testing my access. I guess the important thing is how to
fix it? Do I just change the externals back to point to
the trunk and then commit? </div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>- Bob</div>
<div>
<div class="m_-2554627419769191044m_5731431828596589077m_2973268618336821312h5"><br>
<div>
<div>On May 18, 2017, at 3:15 PM, Samuel Trahan -
NOAA Affiliate <<a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a>>
wrote:</div>
<br class="m_-2554627419769191044m_5731431828596589077m_2973268618336821312m_5745353129908729111Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">Bob,
<div><br>
</div>
<div>Someone modified the trunk externals. You
may have done that by accident when attempting
to modify your branch or commit to the trunk.
The trunk points to a branch that does not
exist at the specified revision (90130, I
think).</div>
<div><br>
</div>
<div>Sincerely,</div>
<div>Sam Trahan</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, May 18, 2017 at
3:49 PM, Robert Oehmke <span dir="ltr"><<a href="mailto:robert.oehmke@noaa.gov" target="_blank">robert.oehmke@noaa.gov</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Hi Sam,
<div><br>
</div>
<div> The bob branch is what I made from
your instructions awhile ago and what
I’ve been working in. Is the reason
that you’re not seeing it because it’s
just local to me? </div>
<div><br>
</div>
<div> As far as I know I haven’t modified
the externals. At one point I edited the
externals file following your
instructions to work on a branch, but
that was months ago. </div>
<div><br>
</div>
<div>While I’m talking to you I have a
question about what information you
want by May 19th. Is the information you
want who needs access to what in general
(independent of whether they already
have it or not), or who needs *new*
access to what (i.e. that is if they
already have access to something, you
don’t want to hear about it). </div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>- Bob</div>
<div><br>
<div>
<div>
<div class="m_-2554627419769191044m_5731431828596589077m_2973268618336821312m_5745353129908729111h5">
<div>On May 18, 2017, at 1:31 PM,
Samuel Trahan - NOAA Affiliate
<<a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a>>
wrote:</div>
<br class="m_-2554627419769191044m_5731431828596589077m_2973268618336821312m_5745353129908729111m_495984220738753691Apple-interchange-newline">
</div>
</div>
<blockquote type="cite">
<div>
<div class="m_-2554627419769191044m_5731431828596589077m_2973268618336821312m_5745353129908729111h5">
<div dir="ltr">
<div>
<div>Hi,<br>
<br>
</div>
The WAM-IPE trunk points to
a non-existent "bob" branch
of NEMS. Did someone change
that external by accident?<br>
<br>
</div>
WAM-IPE trunk:<br>
<div><br>
<a href="https://svnemc.ncep.noaa.gov/projects/nems/apps/WAM-IPE/trunk" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/apps/WAM-IPE/trun<wbr>k</a><br>
<br>
</div>
<div>externals:<br>
<br>
svn propget svn:externals <a href="https://svnemc.ncep.noaa.gov/projects/nems/apps/WAM-IPE/trunk" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/apps/WAM-IPE/trun<wbr>k</a><br>
NEMS -r90130
<a href="https://svnemc.ncep.noaa.gov/projects/nems/branches/WAM-IPE/bob" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/branches/WAM-IPE/<wbr>bob</a><br>
NEMS/src/atmos/gsm -r90126
<a href="https://svnemc.ncep.noaa.gov/projects/gsm/branches/WAM-IPE/quasitrunk" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/gsm/branches/WAM-IPE/q<wbr>uasitrunk</a><br>
NEMS/src/atmos/nmm -r85687
<a href="https://svnemc.ncep.noaa.gov/projects/nems/external_comps/NMM" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/external_comps/NM<wbr>M</a><br>
IPELIB
<a href="https://github.com/IonospherePlasmasphereElectrodynamics/ipe/branches/bob" target="_blank">https://github.com/IonosphereP<wbr>lasmasphereElectrodynamics/ipe<wbr>/branches/bob</a><br>
IPE -r85943
<a href="https://svnemc.ncep.noaa.gov/projects/ipe/branches/nuopc_cap" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/ipe/branches/nuopc_cap</a><br>
DATAWAM -r73436
<a href="https://svnemc.ncep.noaa.gov/projects/nems/external_comps/DATAWAM/trunk" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/external_comps/DA<wbr>TAWAM/trunk</a><br>
DATAIPE -r65981
<a href="https://svnemc.ncep.noaa.gov/projects/nems/external_comps/DATAIPE/trunk" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/external_comps/DA<wbr>TAIPE/trunk</a><br>
<br>
</div>
<div>The "bob" branch of
WAM-IPE does not exist at
that revision. <br>
<br>
svn info <a href="https://svnemc.ncep.noaa.gov/projects/nems/branches/WAM-IPE/bob@90130" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/branches/WAM-IPE/<wbr>bob@90130</a><br>
svn: warning: W170000: URL '<a href="https://svnemc.ncep.noaa.gov/projects/nems/branches/WAM-IPE/bob" target="_blank">https://svnemc.ncep.noaa.gov/<wbr>projects/nems/branches/WAM-IPE<wbr>/bob</a>'
non-existent in revision
90130<br>
<br>
</div>
</div>
</div>
</div>
______________________________<wbr>_________________<br>
WAM-IPE mailing list<br>
<a href="mailto:WAM-IPE@lstsrv.ncep.noaa.gov" target="_blank">WAM-IPE@lstsrv.ncep.noaa.gov</a><br>
<a href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/wam-ipe" target="_blank">https://www.lstsrv.ncep.noaa.g<wbr>ov/mailman/listinfo/wam-ipe</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote><p><br>
</p>
</div></div></div>
</blockquote></div><br></div>
______________________________<wbr>_________________<br>WAM-IPE mailing list<br><a href="mailto:WAM-IPE@lstsrv.ncep.noaa.gov" target="_blank">WAM-IPE@lstsrv.ncep.noaa.gov</a><br><a href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/wam-ipe" target="_blank">https://www.lstsrv.ncep.noaa.g<wbr>ov/mailman/listinfo/wam-ipe</a><br></blockquote></div><br></div></div></div></blockquote></div><br></div>
</blockquote></div><br></div></div></div></div></div></blockquote></div><br></div>
</blockquote></div><br></div></div></body></html>