talk for NN mins questions later ======================================== maintainers maintaining own package everyone else NMUers sponsors sponsees teams working on cross-package transitions BSP participants cross-package goals (reproducible builds) first, 2nd group 1 dgit treat Debian archive as a git repo dgit clone dgit fetch git fetch (eg, sponsee's branch) dgit push 2 what dgit is not replacement for git-dpm git-buildpackage git (except when fetching/pushing from/to Debianish archives) pristine-tar git-import-dsc git-import-dscs intended to be complementary to existing packaging tools 3 example non-maintainer workflows push demo ? sponsor diff experimental vs unstable vs wheezy ======================================== then maintainers how can you help pls use dgit push kthxbye what's in it for you directly merge/cherrypick nmus, proposed patches your real history visible at browse.dgit.d.o. your downstream dgit users will thank you extra check that you are uploading exactly HEAD (can save some dsc-based checks) maintainer operations which change with dgit Need correct style of branch trivially true for native packages true for git-dpm true for raw git with 1.0+diff gbp Use dgit to build (-I .git) NOT dput, but dgit push NMU incorporation - can be done with `dgit fetch' - resulting git history may need fettling - git merge -s ours just before push 4 who should be using it right now source format git workflow tool NMUer maintainer sponsor etc. 1.0 native any ALL ALL 1.0 with diff raw git ALL YES * 3.0 (quilt) git-dpm YES YES * 3.0 (quilt) gbp YES ??? future plans DELAYED uploads automatic sending of the NMU diff email source-only one step push use of the dgit git repo server (other branches and tags) for general purpose work more assistance for use with raw git work needed gbp integration sponsor queue