RE: Working with unmergeable files

Hi Braulio,
 
The best approach for "unmerge able" files like word document and images is to serialize development. This can be neatly implemented in Subversion using the svn:needs-lock property.
 
Thanks
Lakshman

________________________________

From: braulio.horta@embraer.com.br [mailto:braulio.horta@embraer.com.br]
Sent: Tuesday, 18 December 2007 6:32 AM
To: users@subversion.tigris.org
Subject: Working with unmergeable files

I have a kind of best practices question.
Is it possible to make parallel development with unmergeable files? For me it really seems impossible.
How do you work with unmergeable files? Just serialize its development? Break it in smaller files? what else?

Braulio M. Horta

________________________________

This message is intended solely for the use of its addressee and may contain privileged or confidential information. If you are not the addressee you should not distribute, copy or file this message. In this case, please notify the sender and destroy its contents immediately.
Esta mensagem é para uso exclusivo de seu destinatário e pode conter informações privilegiadas e confidenciais. Se você não é o destinatário não deve distribuir, copiar ou arquivar a mensagem. Neste caso, por favor, notifique o remetente da mesma e destrua imediatamente a mensagem.

================================================================================================
EMAIL DISCLAIMER

This email and any attachments are confidential. They may also be subject to copyright.

If you are not an intended recipient of this email please immediately contact us by replying
to this email and then delete this email.

You must not read, use, copy, retain, forward or disclose this email or any attachment.

We do not accept any liability arising from or in connection with unauthorised use or disclosure
of the information contained in this email or any attachment.

We make reasonable efforts to protect against computer viruses but we do not accept liability
for any liability, loss or damage caused by any computer virus contained in this email.
================================================================================================
Received on Mon Dec 17 23:45:38 2007