X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=TODO.BRANCH;h=ba76b1687e2210da81f1b7335ce9e521845fdb0f;hp=0b28a74104d6885aa2fe68f68bae9e1cc903016d;hb=8dba4a073d1eddca7e15ad60d7d5c21d016e60fc;hpb=e0b5aa648f47d5ec6f3368b23f4aeada81f45546

diff --git a/TODO.BRANCH b/TODO.BRANCH
index 0b28a741..ba76b168 100644
--- a/TODO.BRANCH
+++ b/TODO.BRANCH
@@ -1,16 +1,3 @@
-Tag rename unfinished business
-(things resulting from searching for `tag' where searching for
- `debiantag' wouldn't find them)
-
- - protocol version 4
-      implies ability to sign new tag (this is already there
-         so simply advertising version 4 will work)
-      needs also new ability to sign old-format tag in split
-         brain way
-
- - many actual tests
-
- - other tag should be [dgit Maintainer-Tag quilt=$quilt-mode]
 
  - in dopush (?), we need to sort out synthetic fast forard
     this should not depend entirely on quilt mode
@@ -19,18 +6,16 @@ Tag rename unfinished business
        and maybe make fake merge, maybe in dgit view, maybe
        elsewhere ?
 
- - there is some confusion between $split_brain (did we actually
-   generate any commits) and quiltmode_splitbrain (might we have done,
-   including in previous pushes); search for $split_brain and check
-   that use sites are correct
-
 
 Want tests for
+
  - start repo with old tag, push with new tag, run
    "old" dgit to push again with new tag, push again with
    old tag
+
  - rejecting push of same version with one tag when then the other
 
+
 Test that, where appropriate, maint view tags are pushed to dgit git repo
 
 
@@ -38,44 +23,22 @@ Test that, where appropriate, maint view tags are pushed to dgit git repo
 
  * Document --quilt=unapplied|gbp|dpm
 
- * Mention new --quilt=* in debian/changelog
-
- * Mention in-archive copy fix in debian/changelog
-
- * Test --quilt=*
+ * Mention new tag format in debian/changelog
 
+ * Mention new --quilt=* in debian/changelog
 
- * IN ARCHIVE COPY Consider and implement fast-forward fixup
-
-    - On fetch, check if specified git hash is ff from
-      existing dgit branch, the same way we do for constructed
-      dscs.  The .dsc tells us the git tree but not necessarily
-      the git hash.
+ * Test all three new --quilt=unapplied|gbp|dpm
 
-    ...ERR MAYBE...
-      
-         complicated there are many branches
-	       dgit-repos: refs/dgit/suite
-               archive dsc
-	       local; remotes/dgit/dgit/suite
-	                  must be ff
-			  may contain dscs
-               local: dgit/suite (not relevant to fetch)
+ * Mention in-archive copy fix in debian/changelog
 
-         archive dsc must always be regarded
-	       as ff from (or same as) dgit-repos
-               err depending on version number ?
+ * Mention in changelog that:
+   Remove lrfetchrefs at end of fetch_from_archive, for tidyness
 
-       this code is what needs changing
-       	} else {
-	    fail "git head (".lrref()."=$lastpush_hash) is not a ".
-		"descendant of archive's .dsc hash ($dsc_hash)";
-	}
-       it just needs to generate the fake merge and set $hash
-       the archive skew stuff is all fine with this
+ * Want drs-quilt-gbp test.
 
-        xxx actually, no, we need to stop from squashing our
-	lrref with + updates
+ * Mention on changelog or docs that we no longer set a fetch spec for
+   the dgit remote (which doesn't really work anyway)
 
- * Add in-archive-move test case
+ * Split quilt-gbp-build-modes into one with sbuild and one without
 
+ * Add t-tstunt-parsechangelog to various tests