Differences between revisions 5 and 6
Revision 5 as of 2017-11-14 11:45:05
Size: 357
Editor: JulianFoad
Comment:
Revision 6 as of 2017-11-23 23:00:35
Size: 1502
Editor: JulianFoad
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
== Potential Topics to Discuss/Fix/Develop == <<TableOfContents(2)>>
Line 9: Line 9:
* ... == Topics Discussed/Fixed/Developed ==
Line 11: Line 11:


== Discussion Notes ==
=== Releasing 1.10 ===
Line 17: Line 15:
=== View Specs ===

Requirement (Johan): export the sparse configuration of one WC and make another one match it.

Solution (Bert): We can use the WC-state 'Reporter' to find all the info we need -- including depth changes, switched URLs (if wanted), and mixed revisions (if wanted) -- and write this to a simple text format output. For a first hack, the output format could even be a series of "svn update --set-depth=..." lines which could be executed directly by a shell, avoiding the need to write any parse-and-execute code at all.

Also this output is just what we need to record the WC base state of a shelved patch.

Problem: The "update --set-depth" approach doesn't perform well. To apply the desired depths, it would first set the WC root to its desired recorded depth (typically empty or depth-infinity), even if most of the children are going to be excluded; then exclude each child that is to be excluded and expand each that is to be included, and so on. Inefficient. Local mods probably not handled properly.

Solution: TBD

=== Obliterate ===

What hackathon is complete without a discussion of obliterate?

Aachen2017MeetAndGreet -- meet-and-greet event, 23rd November 2017

Aachen2017Practicalities -- location, schedule, etc.


Topics Discussed/Fixed/Developed

Releasing 1.10

...

View Specs

Requirement (Johan): export the sparse configuration of one WC and make another one match it.

Solution (Bert): We can use the WC-state 'Reporter' to find all the info we need -- including depth changes, switched URLs (if wanted), and mixed revisions (if wanted) -- and write this to a simple text format output. For a first hack, the output format could even be a series of "svn update --set-depth=..." lines which could be executed directly by a shell, avoiding the need to write any parse-and-execute code at all.

Also this output is just what we need to record the WC base state of a shelved patch.

Problem: The "update --set-depth" approach doesn't perform well. To apply the desired depths, it would first set the WC root to its desired recorded depth (typically empty or depth-infinity), even if most of the children are going to be excluded; then exclude each child that is to be excluded and expand each that is to be included, and so on. Inefficient. Local mods probably not handled properly.

Solution: TBD

Obliterate

What hackathon is complete without a discussion of obliterate?


Thanks to Assembla for sponsoring SVN Hackathon 2017.

Aachen2017 (last edited 2018-02-23 09:04:38 by JulianFoad)