<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I saw that ... excellent! I will slowly but surely move the GsDevKit
    references to the SeasideSt/Grease repo ...<br>
    <br>
    <div class="moz-cite-prefix">On 07/12/2015 06:05 AM, Johan Brichau
      wrote:<br>
    </div>
    <blockquote
      cite="mid:8BBB7F3F-BD00-47B3-B75F-E0011126737D@inceptive.be"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      Hi Dale,
      <div class=""><br class="">
      </div>
      <div class="">fyi: I just did the ‘swap’ you mentioned.</div>
      <div class=""><br class="">
      </div>
      <div class="">I propose to keep the code for Gemstone in the
        master branch and just keep working as before (i.e. all
        platforms that were tested will remain tested on
        SeasideSt/Grease). </div>
      <div class="">The only difference for now is that GsDevKit will
        have to synchronize its fork when Grease moves forward.</div>
      <div class=""><br class="">
      </div>
      <div class="">Johan</div>
      <div class=""><br class="">
      </div>
      <div class="">
        <div>
          <blockquote type="cite" class="">
            <div class="">On 16 Jun 2015, at 11:17, Dale Henrichs &lt;<a
                moz-do-not-send="true"
                href="mailto:dale.henrichs@gemtalksystems.com" class="">dale.henrichs@gemtalksystems.com</a>&gt;
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <meta content="text/html; charset=windows-1252"
                http-equiv="Content-Type" class="">
              <div bgcolor="#FFFFFF" text="#000000" class=""> Johan,<br
                  class="">
                <br class="">
                I think a better solution would be to merge the changes
                for SeasideSt/Grease into GsDevKit/Grease ... then move
                the GsDevKit/Grease project to SeasideSt/Grease, then
                fork SeasideSt/Grease on GsDevKit .... <br class="">
                <br class="">
                This would avoid any conflicts for the GsDevKit/Grease
                users and then make the SeasideSt/Grease project the
                master project ...<br class="">
                <br class="">
                We did a similar move when we moved projecs from glassdb
                to GsDevKit ...<br class="">
                <br class="">
                Presumably there aren't a lot of SeasideSt/Grease users
                at the moment?<br class="">
                <br class="">
                Dale<br class="">
                <br class="">
                <div class="moz-cite-prefix">On 6/15/15 11:47 AM, Dale
                  Henrichs wrote:<br class="">
                </div>
                <blockquote
                  cite="mid:557F1DBB.6070709@gemtalksystems.com"
                  type="cite" class="">
                  <meta content="text/html; charset=windows-1252"
                    http-equiv="Content-Type" class="">
                  There is probably a way to merge the commits between
                  the two repos and let the SeasideSt/Grease project
                  take precedence  ... <br class="">
                  <br class="">
                  Dale<br class="">
                  <br class="">
                  <div class="moz-cite-prefix">On 06/15/2015 11:17 AM,
                    Johan Brichau wrote:<br class="">
                  </div>
                  <blockquote
                    cite="mid:7E1B4433-5466-4129-8A96-71F704E4FC0D@inceptive.be"
                    type="cite" class="">
                    <meta http-equiv="Content-Type" content="text/html;
                      charset=windows-1252" class="">
                    <br class="">
                    <div class="">
                      <blockquote type="cite" class="">
                        <div class="">On 15 Jun 2015, at 20:13, Dale
                          Henrichs &lt;<a moz-do-not-send="true"
                            href="mailto:dale.henrichs@gemtalksystems.com"
                            class="">dale.henrichs@gemtalksystems.com</a>&gt;


                          wrote:</div>
                        <br class="Apple-interchange-newline">
                        <div class=""><span style="font-family:
                            Helvetica; font-size: 12px; font-style:
                            normal; font-variant: normal; font-weight:
                            normal; letter-spacing: normal; line-height:
                            normal; orphans: auto; text-align: start;
                            text-indent: 0px; text-transform: none;
                            white-space: normal; widows: auto;
                            word-spacing: 0px;
                            -webkit-text-stroke-width: 0px;
                            background-color: rgb(255, 255, 255); float:
                            none; display: inline !important;" class="">Are
                            there differences between the two in terms
                            of packaging/structure? Or is mainly the
                            comit stream that you are thinking of?</span></div>
                      </blockquote>
                    </div>
                    <br class="">
                    <div class="">The commit stream and the Metacello
                      load conflicts for everyone.</div>
                    <div class="">There are no package differences (at
                      least there should not be any) as the repositories
                      for Grease are all the same. However, manually
                      keeping track of changes to both the Smalltalkhub
                      repo and the GsDevKit one, is not an option in the
                      long run either.</div>
                    <div class=""><br class="">
                    </div>
                    <div class="">Johan</div>
                    <br class="">
                    <fieldset class="mimeAttachmentHeader"></fieldset>
                    <br class="">
                    <pre class="" wrap="">_______________________________________________
seaside mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a>
</pre>
                  </blockquote>
                  <br class="">
                </blockquote>
                <br class="">
              </div>
              _______________________________________________<br
                class="">
              seaside mailing list<br class="">
              <a moz-do-not-send="true"
                href="mailto:seaside@lists.squeakfoundation.org"
                class="">seaside@lists.squeakfoundation.org</a><br
                class="">
<a class="moz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br
                class="">
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
seaside mailing list
<a class="moz-txt-link-abbreviated" href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a>
<a class="moz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>