You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to get a warning if the file on the server is newer than the local file when pushing. Overwriting someone else's work is a very easy mistake to make.
The text was updated successfully, but these errors were encountered:
I don't think the file on the server will ever be newer than the file being pushed. I would need to keep track of more data about the files. When fetching a file I would need to save the SystemModStamp somewhere, then before saving I would need to query the file to get the SystemModStamp for comparison. Doable, but not trivial.
thanks for the quick response, I'll keep thinking about it too. I wonder if
a local git repo could help where before every push a fetch and merge is
done. idk, just thinking out loud
On Mon, Oct 12, 2015 at 5:17 PM, Dave Carroll [email protected]
wrote:
I don't think the file on the server will ever be newer than the file
being pushed. I would need to keep track of more data about the files. When
fetching a file I would need to save the SystemModStamp somewhere, then
before saving I would need to query the file to get the SystemModStamp for
comparison. Doable, but not trivial.
—
Reply to this email directly or view it on GitHub #19 (comment)
.
It would be useful to get a warning if the file on the server is newer than the local file when pushing. Overwriting someone else's work is a very easy mistake to make.
The text was updated successfully, but these errors were encountered: