On Apr 21, 2010, at 4:39 PM, verizon wrote:
> I am working on a project with another developer and we are using a
> server hosted fossil repository and have hit this problem. When say
> I make changes to some source files, commit this to the repository
> and sync with the network server. The other developer then sync's
> with the repository but then fossil update does not show any changes
> needed. So he does not see any file changes with command:
>
> fossil update -n -v | grep -v UNCHANGED
>
> We have found (at least for now) the easiest approach is to blow
> away his source files, do fossil open to his (synched) local
> repository and then he has the updated files.
>
> I know I am missing something really obvious here as I thought just
> this situation was what source control systems were for. I had not
> noticed this previously since I was the only one using the repository.
>
This might happen if the you and the other developer are on separate
branches or forks. Try running
fossil update --latest
And/or run "fossil ui" and look at the graph to see whether or not you
are on separate forks, and if so, merge them together.
If you just run "fossil update" it moves you to the latest check-in
which is a direct descendent of your current check-in. So if another
developer has made check-ins that are on a different branch or fork,
nothing will happen.
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
