Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (athena.apache.org: 208.10.26.74 is neither permitted
 nor denied by domain of lesmikesell@gmail.com)
Message-ID: <4D2CB2E3.70407@gmail.com>
Date: Tue, 11 Jan 2011 13:43:31 -0600
From: Les Mikesell <lesmikesell@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: users@subversion.apache.org
Subject: Re: Feature Request: [Was: Best way to maintain patches to a 3rd
 party library?]
References: <AANLkTi=g18Z+_N6vb7z_38xW8LSnqMiOrmNh_4gaQ-5K@mail.gmail.com>
	<20110111180200.GB20710@ted.stsp.name>
 <AANLkTimFBn-4Y9pRzeF7WLjk9MupZRtn4dJoaPxe6ThB@mail.gmail.com>
In-Reply-To: <AANLkTimFBn-4Y9pRzeF7WLjk9MupZRtn4dJoaPxe6ThB@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 1/11/2011 12:36 PM, NN Ott wrote:
>
>
>     It sounds like what you really want is commit access to the upstream
>     Subversion repository, possibly restricted to a special branch.
>     Then your change identifiers would be in the same universe.
>
>
>
> I just want the svn copy/log/diff/merge logic to see past, and account
> for, and svn:external barrier.   Very much a one-way flow of changes.

If the changes are really one-way, they'd all be coming from the 
upstream repository.  If you make changes in 2 places, that's a 
distributed system - even if your copy is never pushed back upstream.

>   Imho, doesn't seem too bizzare or non-svn like.

The svn way is to get write access to a branch in the one-and-only 
repository if you also want to make changes that are tracked.  Or 
reproduce the upstream commits in your copy letting the revision numbers 
(and any external tracking references) get out of sync.

-- 
   Les Mikesell
    lesmikesell@gmail.com