On Fri, Aug 5, 2016 at 10:06 AM, Vincent Lefevre wrote:
> On 2016-08-03 16:10:16 +0200, Stefan Hett wrote:
>> On 8/3/2016 3:40 PM, Nico Kadel-Garcia wrote:
>> > [export/import instead of dump/load]
> [...]
>> In your export/import approach you would do:
>> export -> import -> export -> compare old
On 2016-08-03 16:10:16 +0200, Stefan Hett wrote:
> On 8/3/2016 3:40 PM, Nico Kadel-Garcia wrote:
> > [export/import instead of dump/load]
[...]
> In your export/import approach you would do:
> export -> import -> export -> compare old vs. new export
> And like with the dump/load/dump approach above
On 2016-08-03 09:40:59 -0400, Nico Kadel-Garcia wrote:
> I don't insist on it: it's not always the correct answer. But it's not
> the only time dump/load has suffered from bugs, and I'm sure it won't
> be the last.
Yes, there have been several issues in the past, but people care
about these issues
On 8/3/2016 3:40 PM, Nico Kadel-Garcia wrote:
On Wed, Aug 3, 2016 at 9:02 AM, Ryan Schmidt
wrote:
On Aug 3, 2016, at 7:54 AM, Nico Kadel-Garcia wrote:
On Wed, Aug 3, 2016 at 2:16 AM, Ryan Schmidt wrote:
On Aug 2, 2016, at 9:54 PM, Nico Kadel-Garcia wrote:
On Tue, Aug 2, 2016 at 7:15 AM, Iv
On Wed, Aug 3, 2016 at 9:02 AM, Ryan Schmidt
wrote:
>
> On Aug 3, 2016, at 7:54 AM, Nico Kadel-Garcia wrote:
>
>> On Wed, Aug 3, 2016 at 2:16 AM, Ryan Schmidt wrote:
>>>
>>> On Aug 2, 2016, at 9:54 PM, Nico Kadel-Garcia wrote:
>>>
On Tue, Aug 2, 2016 at 7:15 AM, Ivan Zhakov wrote:
[
On Aug 3, 2016, at 7:54 AM, Nico Kadel-Garcia wrote:
> On Wed, Aug 3, 2016 at 2:16 AM, Ryan Schmidt wrote:
>>
>> On Aug 2, 2016, at 9:54 PM, Nico Kadel-Garcia wrote:
>>
>>> On Tue, Aug 2, 2016 at 7:15 AM, Ivan Zhakov wrote:
>>>
>>> [dump/load cycles omitted]
>>>
>>> Please note. This sort of
On Wed, Aug 3, 2016 at 2:16 AM, Ryan Schmidt
wrote:
>
> On Aug 2, 2016, at 9:54 PM, Nico Kadel-Garcia wrote:
>
>> On Tue, Aug 2, 2016 at 7:15 AM, Ivan Zhakov wrote:
>>
>> [dump/load cycles omitted]
>>
>> Please note. This sort of pernicious bug is why I suggest takeing a
>> clean export/import whe
On Aug 2, 2016, at 9:54 PM, Nico Kadel-Garcia wrote:
> On Tue, Aug 2, 2016 at 7:15 AM, Ivan Zhakov wrote:
>
> [dump/load cycles omitted]
>
> Please note. This sort of pernicious bug is why I suggest takeing a
> clean export/import when moving to significantly newer versions, or
> significantly
On Tue, Aug 2, 2016 at 7:15 AM, Ivan Zhakov wrote:
[dump/load cycles omitted]
Please note. This sort of pernicious bug is why I suggest takeing a
clean export/import when moving to significantly newer versions, or
significantly new project versions, for Subversion repositories. Don't
hurt yourse
On 2 August 2016 at 14:01, Stefan Hett wrote:
> On 7/31/2016 11:54 PM, Johan Corveleyn wrote:
>>
>> On Sun, Jul 31, 2016 at 5:55 PM, Stefan wrote:
>>>
>>> Hi,
>>>
>>> I went through a long overdue dump/load cycle of our main repository and
>>> am wondering atm about a difference I see when compar
On 7/31/2016 11:54 PM, Johan Corveleyn wrote:
On Sun, Jul 31, 2016 at 5:55 PM, Stefan wrote:
Hi,
I went through a long overdue dump/load cycle of our main repository and
am wondering atm about a difference I see when comparing the dump of the
repository with the original dump.
There are a few
On Sun, Jul 31, 2016 at 5:55 PM, Stefan wrote:
> Hi,
>
> I went through a long overdue dump/load cycle of our main repository and
> am wondering atm about a difference I see when comparing the dump of the
> repository with the original dump.
>
> There are a few (at a guess around 20-50) difference
Hi,
I went through a long overdue dump/load cycle of our main repository and
am wondering atm about a difference I see when comparing the dump of the
repository with the original dump.
There are a few (at a guess around 20-50) differences of the following
structure (using fc [olddump] [newdump] o
13 matches
Mail list logo
