On Wed, Oct 23, 2013 at 7:04 AM, Edward K. Ream <edream...@gmail.com> wrote:
> Correct. The shadow files, starting with x_, are *private* files. The > whole point is that they can *not* to be shared. They are your own > personal view of the data in the public files. > ... > If your team members are indeed anti-social, then the only thing you can > do is to share the supposedly *private* @shadow files. Once again, you > have to have *some* cooperation from your supposedly helpful team members. > You will have to add the .leo_shadow directories to your SCCS. > Actually, this won't work very well, for at least one, and probably other, reasons. The problem with committing .leo_shadow directories is that you must synchronize the pushing of public and private files. Synchronizing pushes using a bzr push hook is conceivable, but it creates another synchronization problem: every member of the so-called team must use the same bzr hook! Imo, any scheme requiring synchronized bzr pushes is too fragile to be good engineering. YMMV. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
