Your message dated Mon, 22 Jul 2019 21:08:27 +0000
with message-id <[email protected]>
and subject line Bug#926656: fixed in dgit 9.5
has caused the Debian Bug report #926656,
regarding git-debrebase docs are intimidating
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
926656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926656
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-debrebase
Version: 8.4
Sam Hartman wrote the following me in private email. It is a apposite
(and sadly hilarious) critique of the documentation. I am filing it
here as a bug, with permission.
Ian.
-8<-
From: Sam Hartman <[email protected]>
To: Ian Jackson <[email protected]>
Subject: Re: git debrebase is cool
Date: Sat, 06 Apr 2019 13:01:57 -0400
>>>>> "Ian" == Ian Jackson <[email protected]> writes:
Ian> Did you see dgit-maint-debrebase(7) ?
No.
I'll read it, but before doing so I'll respond with my user hat on:
1) I want to learn about git-debrebase, not about dgit. Dgit is really
scary and I'm told this thing is better than gbp pq.
2) I started with git-debrebase (1) It told me I needed to read
git-debrebase(5) before I had any hope of understanding it. So I went
and looked up how to look at a man 5 page when there is also a man 1
page (OK, I as Sam actually already knew this), and with great
trepidation stopped reading git-debrebase to read this other thing.
3) I started to see a reference to one of those terms from git-debrebase
(1) (anchor), but it tricked me and was just a cross reference to a
detailed branch specification. I don't want to learn a detailed
specification of anything just to go update my patch. Is this going to
be like that time when my friend told me git grafts could solve that
mismerge problem I had and I ended up trying to understand the
gitrepository man page?
4) Then there are diagrams of merge histories. Wait, this is starting
to remind me of the git-rebase man page that I never understood. O,
wait, rebase is in the name. This is not good! And then there is all
this illegal operations stuff!!! Help!
5) Eventually come back to the git-debrebase man page. Wait this really
isn't so bad. I think I might kind of understand things. Except I
totally don't know how to manage my orig tarballs, or my upstream tags
or anything. I guess I can use gbp for that, but then why don't I use
gbp for everything.
To be clear, I appreciate the detailed documentation, data model and
description of invarients. I did find it took me a lot longer to go
through than the gbp documentation, but I'm the kind of person who found
this detail helpful.
But in contranst gbp-pq mentions rebase once. It allows the user to
think they are not going to need to understand any of the more complex
git stuff, where as git-debrebase tells you right there that rebase -i
might be something you want to do often.
And yeah, you and I probably do want to rebase -i quite often.
But there are a lot of people who never understand git that well. I
don't have a handle on the skill of the average DD nor what the tail
looks like. When I joined Debian, the developers I interacted with were
all fairly skilled. And yet watching discussion of git, git-dpm and
dgit in #debian-devel, I think a lot of people find them beyond their
comfort level.
I don't know what the answer is. I don't even know for sure this is a
problem. I know I want to be in a world where I get to be using tools
like git-debrebase or git-dpm. I would rather live in a world where we
all use gbp pq than where we never get to anything uniform, but that
would not be my first choice.
-8<-
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 9.5
We believe that the bug you reported is fixed in the latest version of
dgit, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sean Whitton <[email protected]> (supplier of updated dgit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 22 Jul 2019 21:38:19 +0100
Source: dgit
Architecture: source
Version: 9.5
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson <[email protected]>
Changed-By: Sean Whitton <[email protected]>
Closes: 857490 926656 932459 932477 932536 932612 932630 932694
Changes:
dgit (9.5) unstable; urgency=medium
.
git-debpush [Sean Whitton]:
* Support ignoring individual checks with --force=check. Closes:#932459.
* Check upstream source is identical in the upstream tag.
* Check that patches are (un)applicable. Closes:#932477.
* Check for an unstitched git-debrebase branch. Closes:#932612.
* Check for explicitly pushing detached HEAD.
.
dgit clone [Ian Jackson]:
* No longer create an "origin" remote. Closes:#932694.
.
Documentation:
* dgit-maint-bpo(7): new manpage for maintainers of official Debian
backports. Closes:#857490. [Sean Whitton]
* git-debrebase(1): make this manpage a less intimidating entry point.
Closes:#926656.
[Sean Whitton & Ian Jackson; prompted by feedback from Sam Hartman]
.
Miscellaneous:
* Correct the description of --force in git-debpush(1) [Sean Whitton].
* git-debrebase(*): fix some crossreferences [Sean Whitton].
Closes:#932536.
* Break out git-playtree-setup and rewrite in shell. [Ian Jackson]
* Fix organisation copyright attribution for Matthew Vernon's
contributions. Closes:#932630.
* HACKING: new document for helping people work on the code. [Ian Jackson]
* Update Vcs-Git etc. to point to salsa.
Checksums-Sha1:
ca180efe4ebb7647f9641e41585e5e8fb805fbfc 2131 dgit_9.5.dsc
8d76f681bd3f1f9d606d32ae445e20c19f4a38b7 688952 dgit_9.5.tar.gz
Checksums-Sha256:
4c0eb3302e6d0529b8601c2a8ce448cc7e9557de53816bee64589047cbc51e7a 2131
dgit_9.5.dsc
d7824911126f7c1a3488d90a05b0bbd257ae7ea5c66c2ab0761dc67e355c11a8 688952
dgit_9.5.tar.gz
Files:
62e98c4739b46a16c1becbb63f5d66c2 2131 devel optional dgit_9.5.dsc
af998cb37cc3c54c1b165a5b39ef1a63 688952 devel optional dgit_9.5.tar.gz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAl02H1cACgkQaVt65L8G
YkAeDw//WCFSJDhusp7JUVpnGKAwwfb1BmqOYYqJy6kH/nmAOvkdCeNGFFuncIAb
Ohr9dPiZdaOSFwvxvV7peoET9EYlryHgWu+bJ5GC60g5O4OYF9urJl3Q7p2/qxxu
kXBsIz2bj4DjvGuU8FsVx7TN7ca/394X5oPXr0PKNp+DMEcHzHgrGBcHYj94x2NU
xhVfd71jX6nBSVX6vBtBqrbFP4ZKHj8SthKdfVxfWHWYTBUUjiDX6Kmlibju40h5
pOEyCbw1QLZPV4NEd0ItwnblYa/PMZbUtWphbAovJVGoiCsUsJQyaDnCEQt3JfrZ
L7JTRRXPuj08xVmYeKyLYC4iw0G5HYRybEvxrTFrl26iBITr9hsb46tNDGO/RMKA
TdHcwg/uD11R7HmXUIfmMDVeZ0uhYuWAcGBeMmKY9Op3nKTNXN3nFyIueecE8Lhg
QqsfQAA/k8EX24ohJcZEMVxeInNusVcS6UF5yPqesfN5VgN4iHNbWFoZzuF1eHdo
q0uaZHmquyBamZ2z+sIlEjl4JLRoob1/t2il77/FvRrGCjoVlyQM3hbmhgFY+G+v
+zxdJCliBU8fsgjyFecoUvv2KFoF4DJzmy/B0NYQUCesM8DTQFT74kPnziiWjDH6
pk2DCQ1y0bKm8e/bZMObEBpGg+dwkVf8+st1lPzYsKNjjG9jM8s=
=ih71
-----END PGP SIGNATURE-----
--- End Message ---
