aboutsummaryrefslogtreecommitdiffstats
path: root/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/ed5eac05-80ed-411d-88a4-d2261b879713/comments/9525e3f3-a044-4fa9-b311-56336267b8b5/body
blob: ae7a57f601a67cb551cfb867c4be52e19f31e5c6 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
> I think a good solution would run along the lines of the currently
> commented out code in duplicate_bugdir(), where a
>   VersionedStorage.changed_since(revision)
> call would give you a list of changed files.  diff could work off of
> that directly, without the need to generate a whole duplicate bugdir.

This is definately the way to go.  Rough approach for the VCS family:

1) Parse `bzr diff` or such to get a list of new,changed,moved,removed
   paths.
2) Convert those paths to ids.
3) Return a list of ids to duplicate_bugdir().
4) Provide Storage.parent(id, revision), so duplicate_bugdir() could
   figure out what type of id we were dealing with (bugdir, bug,
   comment, other?), and construct the appropriate difference tree.

There could be a DupBugDir class which stored that diff tree and a
link to the current bugdir, which would make diffs much easier (work
already done, just copy the diff tree), and provide faster access to
unchanged files (just use the current version).