From: Ian Jackson Date: Mon, 25 Aug 2014 22:13:53 +0000 (+0100) Subject: demo X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ijackson/git?a=commitdiff_plain;h=764d60ecc85efbbfa6921d9af21a782fe76f799d;p=talk-2014-debconf-dgit.git demo --- diff --git a/Makefile b/Makefile index 9410c30..e69c4f7 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ -SLIDES=archive-vcs manpage libavg access-table +SLIDES=archive-vcs manpage demo-placeholder libavg access-table SLIDEFILES=$(addsuffix .ps, $(SLIDES)) diff --git a/demo-placeholder.fig b/demo-placeholder.fig new file mode 100644 index 0000000..4b54f2a --- /dev/null +++ b/demo-placeholder.fig @@ -0,0 +1,10 @@ +#FIG 3.2 Produced by xfig version 3.2.5b +Landscape +Center +Metric +A4 +100.00 +Single +-2 +1200 2 +4 0 0 50 -1 0 24 0.0000 4 345 1185 2745 4500 (demo)\001 diff --git a/talk.txt b/talk.txt index 4140e3e..8f3ccb5 100644 --- a/talk.txt +++ b/talk.txt @@ -37,12 +37,12 @@ whether the maintainer uses dgit, other git tools, quilt, CVS or SCCS. With dgit you do all direct source code management in git. As a dgit user you do not interact with the archive directly. +[demo] + dgit is particularly useful for NMUers: you can prepare an RC bugfix, -with full support from git, withut needing to know anything about the +with full support from git, without needing to know anything about the package's usual VCS arrangements. -[demo] - dgit also has great potential for downstreams - that is, derivatives and users who want to modify a package. Having used dgit clone or fetch, you can merge into your downstream branch. (There are some