{"thread":{"id":"15543","subject":"Re: [PATCH] Optional shrinking of RCS keywords in git-p4","startedAt":"2008-09-16T04:53:34Z","lastAt":"2008-09-16T17:26:33Z","messageCount":2,"participants":["dhruva","Daniel Barkalow"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"90800","messageId":"98627.82548.qm@web95002.mail.in2.yahoo.com","threadId":"15543","inReplyTo":null,"subject":"Re: [PATCH] Optional shrinking of RCS keywords in git-p4","fromName":"dhruva","fromEmail":"dhruva@ymail.com","sentAt":"2008-09-16T04:53:34Z","receivedAt":"2008-09-16T04:53:34Z","isPatch":true,"sender":{"key":"dhruva@ymail.com","avatar":null},"body":"Hi,\n\n\n\n----- Original Message ----\n> From: David Brown <git@davidb.org>\n> Part of the problem is that p4 isn't very good at knowing whether\n> files have changed or not.  'p4 sync' will update the file _if_ if\n> thinks your version is out of date, but it does nothing if someone has\n> locally modified the file, hence the need for the 'p4 sync -f'.\n\nIf you have modified a file without doing a 'p4 edit' and if there is a new version of the edited file on p4 (from what you have got from a previous 'p4 sync'), 'p4 sync' will overwrite your changes (if the file does not have write perm set or if you have enabled clobbering of writable files). Whereas 'p4 sync -f' will always overwrite all unopened files if a newer version is available.\n\n-dhruva\n\n\n\n      Unlimited freedom, unlimited storage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/\n"},{"id":"90850","messageId":"alpine.LNX.1.00.0809161316030.19665@iabervon.org","threadId":"15543","inReplyTo":"98627.82548.qm@web95002.mail.in2.yahoo.com","subject":"Re: [PATCH] Optional shrinking of RCS keywords in git-p4","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2008-09-16T17:26:33Z","receivedAt":"2008-09-16T17:26:33Z","isPatch":true,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Tue, 16 Sep 2008, dhruva wrote:\n\n> Hi,\n> \n> \n> \n> ----- Original Message ----\n> > From: David Brown <git@davidb.org>\n> > Part of the problem is that p4 isn't very good at knowing whether\n> > files have changed or not.  'p4 sync' will update the file _if_ if\n> > thinks your version is out of date, but it does nothing if someone has\n> > locally modified the file, hence the need for the 'p4 sync -f'.\n> \n> If you have modified a file without doing a 'p4 edit' and if there is a \n> new version of the edited file on p4 (from what you have got from a \n> previous 'p4 sync'), 'p4 sync' will overwrite your changes (if the file \n> does not have write perm set or if you have enabled clobbering of \n> writable files). Whereas 'p4 sync -f' will always overwrite all unopened \n> files if a newer version is available.  \n\np4 sync -f will overwrite all unopened files. It will clobber writable \nfiles, and it will clobber files where there isn't a newer file (it's one \nof the ways of dealing with accidentally erasing your workspace).\n\n\t-Daniel\n*This .sig left intentionally blank*\n"}]}