On Thu, Nov 21, 2019 at 3:09 PM Vincent Lefevre wrote:
> On 2019-11-20 15:21:22 +0100, Johan Corveleyn wrote:
> > Vincent Lefevre also wrote:
> > >> Note: "svn cat -r... file2" or "svn cat -r... file2@3" also shows a
> > >> similar behavior:
> > >> -r1: one gets file1@1
> > >> -r2: "Unable to
On 2019-11-21 15:09:05 +0100, Vincent Lefevre wrote:
> Exactly, but the reason is not that file1 was unchanged in r2.
> It is because that file1@1 is the latest ancestor or file2@3.
^^
to be read: "the latest ancestor of file2@3". Sorry for the ty
On 2019-11-20 15:21:22 +0100, Johan Corveleyn wrote:
> Vincent Lefevre also wrote:
> >> Note: "svn cat -r... file2" or "svn cat -r... file2@3" also shows a
> >> similar behavior:
> >> -r1: one gets file1@1
> >> -r2: "Unable to find repository location for..." error
> >> -r3: one gets file2@3
On Tue, Nov 19, 2019 at 4:53 PM Nathan Hartman wrote:
>
> On Mon, Nov 18, 2019 at 4:44 AM Vincent Lefevre
> wrote:
>>
>> I have the following issue with svn 1.10.6:
>>
>> Assume that I committed "file1" at revision 1, did some unrelated
>> change at revision 2, and for revision 3, copied "file1@
On Mon, Nov 18, 2019 at 4:44 AM Vincent Lefevre
wrote:
> I have the following issue with svn 1.10.6:
>
> Assume that I committed "file1" at revision 1, did some unrelated
> change at revision 2, and for revision 3, copied "file1@1" to "file2"
> with "svn copy"[*] and did some changes in file2 bef
I have the following issue with svn 1.10.6:
Assume that I committed "file1" at revision 1, did some unrelated
change at revision 2, and for revision 3, copied "file1@1" to "file2"
with "svn copy"[*] and did some changes in file2 before the commit.
[*] The revision older than the latest one is wha
