On Tue, Feb 24, 2015 at 9:49 AM, David Aldrich
wrote:
> Hi
>
>
>
> My most recent commit was the creation of a tag. I want to delete that tag.
> Should I reverse merge the commit or simply delete the tag?
>
>
>
> If I do a reverse merge I see a tree conflict:
>
>
>
> C:\>svn merge -c -69
>
> ---
Mitch Capper writes:
> I am sorry if missing something but I seem unable to properly compile
> subverison statically. After trying various configure options it continues
> to fail with urls with:
>
>1. # ./subversion/svn/svn checkout http://bing
>2. svn: E17: Unrecognized URL scheme
I am sorry if missing something but I seem unable to properly compile
subverison statically. After trying various configure options it continues
to fail with urls with:
1. # ./subversion/svn/svn checkout http://bing
2. svn: E17: Unrecognized URL scheme for 'http://bing'
3. # ./subver
On Tue, Feb 24, 2015 at 8:49 AM, David Aldrich
wrote:
>
> My most recent commit was the creation of a tag. I want to delete that tag.
> Should I reverse merge the commit or simply delete the tag?
In subversion the usual convention is that tags are never changed
after the copy that creates them.
David Aldrich wrote:
>My most recent commit was the creation of a tag. I want to delete
>that tag. Should I reverse merge the commit or simply delete the tag?
If want to completely remove the tag, not only parts of it, a "svn rm"
is the best match.
It's also less effort because to can delete t
Hi
My most recent commit was the creation of a tag. I want to delete that tag.
Should I reverse merge the commit or simply delete the tag?
If I do a reverse merge I see a tree conflict:
C:\>svn merge -c -69
--- Reverse-merging r69 into '.':
C tags\TAG_
--- Recording mergeinfo for reverse
Hi Bert,
thanks. That mostly does explain the current behavior to me.
From a user's point of view I however find this difference in recorded
mergeinfos quite problematic. While certainly both cases represent the
same logical merge structure:
case 1:
svn:mergeinfo for /B: /A:2-5
case 2:
