Re: Cannot "update"/"commit" from top level bookmark anymore?

Alexander Mueller <[email protected]> Fri, 25 Jan 2013 23:19:09 +0100
Newsgroups gmane.comp.version-control.subversion.rapidsvn.user
Message-ID <[email protected]>
It's a bug, not a feature. Seems like this started when we shipped=20
RapidSVN with svn 1.6.

Am 25.01.2013 22:47, schrieb [email protected]:
> Just figured this out.. the end of the top level bookmark gets included
> in the tree view, just not necessarily at the top.
>
> So you have everything under the bookmark plus one more entry when you
> expand the bookmark.
>
> That entry has everything duplicated under it yet again.
>
> That is pretty confusing.
>
> Why not just display the one top level bookmark derived entry in the
> tree view and then expand below it?
>
> But this feature at least allows a full tree to be updated/committed.
>
> I haven=E2=80=99t experimented what happens if there is a duplicated name=
 in the
> top level of the tree..
>
> Eg: svn://myarchive/project1 as the bookmark, then the first item in the
> archive is also =E2=80=9Cproject1=E2=80=9D.
>
> *From:*Lucas, Andrew T @ ISG - IS
> *Sent:* Tuesday, January 15, 2013 9:54 AM
> *To:* '[email protected]'
> *Subject:* RE: Cannot "update"/"commit" from top level bookmark anymore?
>
> Sorry.. I think this may be Issue #: 547 just reworded..
>
> Looks like it broke between 0.9.4 and 0.9.6 and has been downgraded in
> importance repeatedly to a target of 0.16.
>
> I=E2=80=99m not sure I agree with the priority. It makes the tool much ha=
rder to
> use.
>
> *From:*Lucas, Andrew T @ ISG - IS
> *Sent:* Tuesday, January 15, 2013 8:54 AM
> *To:* '[email protected]'
> *Subject:* Cannot "update"/"commit" from top level bookmark anymore?
>
> Hi,
>
> We just upgraded to v0.12.1 revision 8257 from 0.9.4.
>
> RapidSVN no longer allows you to expand the top level bookmark and then
> execute an update/commit.
>
> You have to work on a subtree within the local working copy / bookmark.
>
> You can still update/commit the entire tree from the command line of
> subversion 1.7.8.
>
> Was this inadvertently taken out of RapidSVN?
>
> You really should have the option on working the whole tree/working copy.
>
> The tree might not be the entire archive.. the working copy might just
> be a subset of the parent tree so forcing people to move everything down
> one level is not realistic and I don=E2=80=99t think is how it was intend=
ed to work.
>
> It used to be that way in rapidsvn until you expanded the top bookmark,
> then you could right click on the expanded bookmark and get a context
> menu that had the update and commit for the full tree.
>
> It no longer allows you to do that.. and it should.
>
> Thanks,
>
> Andy
>

------------------------------------------------------
http://rapidsvn.tigris.org/ds/viewMessage.do?dsForumId=3D671&dsMessageId=3D=
3045951

To unsubscribe from this discussion, e-mail: [[email protected]=
gris.org].