Re: Re: Re: [Subclipse-dev] compile and install subclipse using local update site

On Thu, Apr 29, 2010 at 10:11 AM, elane pereira
<elane.s.pereira_at_gmail.com> wrote:
>> It is not going to be possible to customize Subclipse to commit to two
>> locations.  Subversion cannot do that.
>
> I thought it was possible to modify the action that effects the commit by adding a new repository, in this > case both the trunk clone and branch clone. For example,
>
> currently: commit (content, repository);
>
> Change to: commit (content, repository);
> commit (content, repository 2);
> commit (content, repository 3);

These second two steps cannot be done. Try doing it using the svn
command line client and you will see.

When you do svn commit, you do not get to specify where to commit.
The repository is based on the meta information in your working copy,
and the commit process sends a binary diff to the server. Once the
commit finished the metadata is updated so there are no longer any
local diffs. So once the commit completes you do not even have access
to what has changed anymore.

That is why what you really need to do is merge. Merge would let you
merge the changes to another branch and then commit.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1043&dsMessageId=2598902
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].