Reimplementation of Pijul in C, for education, fun and absolutely no profit

#4 change: make one big list of dependencies, use for reference in output

Opened by laumann on June 2, 2023
laumann on June 2, 2023

In the output of pijul patch, the list of dependencies appear as follows:

message = 'Makefile: add check target'
timestamp = '2022-10-31T12:34:27.238139355Z'

[[authors]]
key = 'AFgzZkD8ARgC21gkkCvxPV5HbL7YDVzgYEhbAxQG7UQY'

# Dependencies
[2] ZYOEB24JLLX7AJG4K4OT3CQKWN6HWHENEN2L5QKUNFUFP5SSZMLAC
[3]+B3XLVPNC4COLLC3FUE34Y7HIKTMF6CJZUASZOU3YM2YGPZKJZP7QC
[*] B3XLVPNC4COLLC3FUE34Y7HIKTMF6CJZUASZOU3YM2YGPZKJZP7QC
[*] 2C2EF2GKTOAT7QI56KKDFGRGSFZRDPKUASNQFB6XQDROAEPPZW4AC
[*] YMWRMSQ6VUDGGA6S5VBJH23PZS44BSGFPPH2B6SBQJZRFXEEGKDAC
[*] ML5XMZEUXMSGA5WS3ZPNKORU5NDAU2XYK676DW6QGXHQAOLCO7EAC

# Hunks

1. Edit in "Makefile":47 3.458 "UTF-8"
  up 3.677, new 0:82, down 3.677
+ check: build
+ 	./ani change AGBLQOQIB6DSD2APO6L2PLFXF7CRWKAD6VAWIAD6F2DTH4EIRYRQC
+ 

2. Replacement in "Makefile":55 3.458 "UTF-8"
B:BD 3.766 -> 2.1557:1587/2
  up 3.766, new 83:119, down
- .PHONY: clean fmt build graph
+ .PHONY: clean fmt build graph check

The numbering (starting from 2 for some reason) is referenced in the Hunks section. Something like “up 3.677, new 0:82, down 3.677” means something like “The patch numbered 3 in this position has a new vertex (one or more lines) after (byte?) position 677 in the file. This new vertex is followed by the changes in the patch numbered 3 (the same as before), position 677”.

“B:BD 3.766 -> 2.1557:1587/2” references patches 2 and 3 (haven’t fully deciphered how).

Patches marked with [*] are indirect dependencies that aren’t directly needed. Patches further marked with “+” are in the “extra known” set.