patchRe: [PATCH] Optional shrinking of RCS keywords in git-p4

> From: David Brown <git@davidb.org>
> Part of the problem is that p4 isn't very good at knowing whether
> files have changed or not.  'p4 sync' will update the file _if_ if
> thinks your version is out of date, but it does nothing if someone has
> locally modified the file, hence the need for the 'p4 sync -f'.

> Hi,
> 
> 
> 
> ----- Original Message ----
> > From: David Brown <git@davidb.org>
> > Part of the problem is that p4 isn't very good at knowing whether
> > files have changed or not.  'p4 sync' will update the file _if_ if
> > thinks your version is out of date, but it does nothing if someone has
> > locally modified the file, hence the need for the 'p4 sync -f'.
> 
> If 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.