What is the recommended procedure for tracking upstream's git history in
a git-dpm managed repository?
Ideally, the commits to git-dpm's upstream branch should probably
inherit from the "real" upstream branch's release commit - either in
addition to or instead of the previous release on git-dpm's upstream
Is there any machinery in place to automate this?
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
Git-dpm-user mailing list