Package: git-debpush
Version: 9.7

I was reviewing various stuff and noticed the following:

* With --force=<check>, the checks are in fact mostly problems.  If
  you read the list, they are things like "unreleased" and
  "upstream-nonidentical".  There is one big exception:
  "patches-applicable".  I suggest we rename it to
  "patches-non-applicable".  We might also consider renaming "suite"
  to "changed-suite" (and leaving "suite" as a convenience alias).
  Maybe the rubric should be changed to --force=<problem>.

* I think -n ought to do nothing, not just not push.  Ie it ought to
  be dry run, like most other commands' -n options.  Maybe -N ?  Or
  "-t" for "--tag-only" ?

* There should be some option which prints the tag message (-m option)
  to stdout.  Constructing that message is the key piece of knowledge
  that git-debpush embodies and it should be useable by itself.

I think we can still change anything we like in this area.

Ian.

-- 
Ian Jackson <ijack...@chiark.greenend.org.uk>   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.

Reply via email to