Re: svn:use-local feature request?

Hi Anya,

Looking at your specific example:-

> A simple example: developer A uses Intel compiler and developer B uses
> GNU. They both checkout a makefile from the repository and change the
> compiler name in the makefile. They then want to commit their code
> modifications, but both wish to keep their own versions of the makefile.

A released product is made up of components which are built using specific
tools ... if you change the compiler you may introduce defects to your
code which are due to the binaries produced by defects in the compiler.
I've actually experienced this one in a previous role where as a sysadmin
we (unthinkingly) patched the central copy of the compiler in order to fix
an issue one team was having ... this however broke the build of one of
another team who were unknowlingly relying on the defect for their code to
work.

As an SCM best practice the version of the tools used to build your
released product should be tracked alongside your source code (IMHO).

Consequently your statement concerning developers wanting to be able to
modify (as an example) makefiles so that they can change the compiler ...
this is exactly the kind of situation you'd want to track in an SCM
system.

YMMV,

Dg.

--
David Grierson
JPMorgan - IB Architecture - Source Code Management Consultant
GDP 228-5574 / DDI +44 141 228 5574 / Email david.x.grierson_at_jpmorgan.com
Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
 
Generally, this communication is for informational purposes only
and it is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation
of any transaction. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s).  All market
prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice.
Any comments or statements made herein do not necessarily reflect
those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org