From 8436e4ded164239453c38f192fe3bde3a4b70635 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Fri, 16 Aug 2013 15:07:33 +0100 Subject: [PATCH] todos --- TODO | 14 +++----------- dgit.1 | 7 +++++++ 2 files changed, 10 insertions(+), 11 deletions(-) diff --git a/TODO b/TODO index a172bd4d..f7c0b7df 100644 --- a/TODO +++ b/TODO @@ -1,18 +1,10 @@ config for repo locations -push should push to dgit remote (other branches) - Archive agility. Archive needs to specify (a) way to get versions and paths in archive for dscs (b) unpriv pull location (c) priv push location -Policy: rc bugs for - server(s?) not reachable - mismatch - -Policy: New field in dsc - specifies - commit hash corresponding to the thing uploaded - optional commit hash corresponding to pristine tar - Vcs-git-master: #commit +Vcs-Git-Master: + specifies commit hash corresponding to the thing uploaded + optional commit hash corresponding to pristine tar?? diff --git a/dgit.1 b/dgit.1 index 3bc270c7..19f38684 100644 --- a/dgit.1 +++ b/dgit.1 @@ -139,6 +139,13 @@ dgit assumes knowledge of the archive layout. There appears to be no sane way to find the path in the archive pool of the .dsc for a particular suite. +Debian Policy needs to be updated to describe the new Vcs-Git-Master +field (and to specify that it is an RC bug for that field to refer +to an unavailable commit). + +dgit push should perhaps do `git push origin', or something similar, +by default. + The mechanism for checking for and creating per-package repos on alioth is a hideous bodge. One consequence is that dgit currently only works for people with push access. -- 2.30.2