From 5d7d18dfe15ce53a1bcdeb8e197bc4e09ef5a8f3 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Wed, 27 Aug 2014 01:48:41 +0100 Subject: [PATCH] mention configure --- talk.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/talk.txt b/talk.txt index 659843c..71a6068 100644 --- a/talk.txt +++ b/talk.txt @@ -77,6 +77,13 @@ the successive dgit uploads must have a fast-forwarding history. Specifically, each upload made with dgit must have as an ancestor the current state of that package in the archive. +I should expand a bit on the need for the git commit to be identical +to the source package. dgit is (amongst other things) a way of +looking at source packages, and their history, using git. That means +that the git tree has to be the same as the package tree. +Specifically, for example, files like configure need to either be in +both git and the source package, or neither. + [ synthetic commit example ] Non-dgit uploads don't have a (suitable) git commit hash. But -- 2.30.2