MSGID: 1:154/10 671e40e4   
   REPLY: 56575.sync_sys@1:103/705 2b83fa52   
   PID: SmapiNNTPd/Linux 2.4.7   
   CHRS: UTF-8 4   
   TZUTC: -0500   
   TID: hpt/lnx 1.9 2024-03-02   
   On Sun, Oct 27 05:23:30 -0500, you wrote:   
      
    k> Working:   
      
    k> /sbbs/exec   
    k> /sbbs/ctrl   
    k> /sbbs/xtrn   
    k> ...   
      
    k> Source Tree:   
      
    k> /sbbs/repo/src   
    k> /sbbs/repo/ctrl   
    k> /sbbs/repo/xtrn   
    k> ...   
      
    k> I have too many of the JS files modified and don't want to accidently   
    k> screw anything up so just copy JS files that have changed/new etc..   
    k> manually I'm sure there are much easier ways to do it, but this is the   
    k> way I do it. works for me :) and theres really not much I have to put   
    k> into it.   
      
   I don't think you're doing anything different that most others here. I think   
   the above setup is pretty standard. At least that's how it is here, as well.   
   The initial 'clone' of git sets it up this way, for the exact purpose that   
   you're not overwriting what you already have going on.   
      
   Any of your modified .JS files should be copied to your /sbbs/mods directory,   
   where they won't be overwritten by git in any case, but will be read by   
   Synchronet before the one located in /sbbs/exec. Once you have that setup, you   
   can safely copy everything from /sbbs/repo/exec to /sbbs/exec after you pull   
   updates from git, rather than tracking what was modified and copying them one   
   at a time, manually.   
      
   The modified .js files in /sbbs/mods will need to be updated/diff'd/merged   
   manually, though. But this is the proper way to separate them so whatever   
   changes you've made don't get overwritten and you can continue to update   
   Synchronet from git without accidentally screwing anything up.   
      
   Sometimes, if my changes to a .js are minimal (a couple/few lines), and the   
   repo changes to the same .js are more substantial than what I've done, I'll   
   just rename my current script, copy the newly updated one to my mods   
   directory, and then copy/paste my changes into the new one. Otherwise, if the   
   repo changes are minimal, I'll just see what the changes (diffs) were on   
   github and add/remove those modifications to the script I'm already using.   
      
   Regards,   
   Nick   
      
   ... Take my advice, I don't use it anyway.   
   --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Thunderb   
    * Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)   
   SEEN-BY: 90/1 103/705 104/119 105/81 106/201 123/10 124/5016 128/187   
   SEEN-BY: 153/757 7715 154/10 30 50 700 203/0 218/700 220/90 221/0   
   SEEN-BY: 221/6 226/30 44 50 227/114 229/110 114 206 317 400 426 428   
   SEEN-BY: 229/470 550 700 705 240/1120 5832 266/512 280/464 5003 5006   
   SEEN-BY: 282/1038 291/111 292/8125 301/1 320/219 322/757 341/66 234   
   SEEN-BY: 342/200 396/45 423/120 460/58 256 1124 467/888 633/280 712/848   
   SEEN-BY: 770/1 2320/105 3634/12 5020/400 5054/30 5075/35   
   PATH: 154/10 280/464 460/58 229/426