<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div> <div style="color:black"><br>From: <span style="color:black">Tobias Jung</span> <a href="mailto:newsgr@tobiasjung.net">newsgr@tobiasjung.net</a><br></div><div style="color:black"><br></div> <blockquote type="cite" class="clean_bq"><span><div><div></div><div><br>If you don't want to or can't use Git/Subversion etc (although I agree that this is the best solution), why don't you just use an FTP client that is capable of syncing when you move the files to production?
<br>
<br>You can tell the FTP client (e.g. YummyFTP, Transmit or as far as I know even the free Cyberduck) only to move the files that are newer than their counterparts on the server, or that have a different file size.
<br>
<br>That way, you don't even have to keep track manually.
<br>
<br></div></div></span></blockquote><div><br></div><div id="bloop_customfont" style="margin: 0px;">For a single feature or bugs that are worked on sequentially this would work well. </div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Unfortunately, I often have more than 1 issue on the go (average is probably 5, i.e. one is in alpha, another in beta, another one is on hold etc.) with the same code base. This method would still require me to keep track somehow of which files belong to which issue. </div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Also my project code bases are often large, in the thousands of files (we’re talking big legacy stuff). Doing any sort of comparison over the full project would take an extraordinary amount of time, I’d think. I’ve really only used Transmit and Cyberduck for a few clients who’s server only allows FTP so I’m not sure how quick these programs are with that sort of stuff - mostly I go command line FTP.</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">I much prefer scp. I have many scripts created that I use to upload with scp so I’d like to continue with them.</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Thanks for the suggestion though. If I’ve missed on how I can work on multiple issues with FTP please let me know.</div><div id="bloop_sign_1401214588865884160" class="bloop_sign"><div style="font-family: helvetica, arial;"><br>Ed</div></div></body></html>