From 57b72bf3294e7d3c8620508a5cd8bfdca04e4f22 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Mon, 12 Aug 2013 19:34:05 +0100 Subject: [PATCH] new thing --- NOTES | 32 ++++++++++++++++++-------------- 1 file changed, 18 insertions(+), 14 deletions(-) diff --git a/NOTES b/NOTES index cd8d5eb0..9254ec6e 100644 --- a/NOTES +++ b/NOTES @@ -1,29 +1,33 @@ New field in dsc specifies - url(s) to clone to get history commit hash corresponding to the thing uploaded optional commit hash corresponding to pristine tar Vcs-git-master: -dget or something +dgit clone fetches dsc - clones repo - repros pristine-tar -what about a git fetch + clones repo from alioth + repros commit if nec. (if no hash in current dsc, check that + dsc is after git head and make synthetic commit, otherwise + complain) -git-buildpackage - adds field for master commit hash - adds field for pristine tar +dgit fetch + as above -dupload (?) - checks isn't a force push into archive? - does signature - does push to server(s) - adds tags to changes file to promise has pushed - does actual upload +dgit push + after git-buildpackage --tag (but no sign) + check repo is clean and tag is made + signs tag + debsign + push to alioth (perhaps with merge -s ours) + dput where on alioth upstream rc bugs for server(s?) not reachable mismatch + +?git-buildpackage +? adds field for master commit hash +? adds field for pristine tar -- 2.30.2