Bug#1127616: developers-reference: should document using git-debpush to upload

Ian Jackson <[email protected]>
Newsgroups gmane.linux.debian.devel.policy
Message-ID <27019.21423.442156.570066__7991.37593000836$1770738690$gmane$org@chiark.greenend.org.uk>
Holger Levsen writes ("Re: Bug#1127616: developers-reference: should document using git-debpush to upload"):
> b.) loosing the information that an upload was sponsored.)

I don't think this is accurate.  The information is not lost.
It's visible in the .changes, and available in UDD, for example.[1]
There is a bug in tracker.d.o, that it isn't displayed.  #1116530.

But, maybe we can sidestep these questions.  Your criticisms don't
apply to uploads done with dgit.  And, indeed dgit push-built is best
practice for NEW uploads:

The improvements for the maintainer, when switching from dput to dgit,
are not trivial.  But, more importantly, dgit push-* is the only way
to publish the source code as git in systematically and reliably
useable and buildable form.  That is a real benefit to our users and
downstreams.

How about a patch that recommends use of dgit for uploads?

Ian.

[1] I don't think the current representation in UDD
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116530#41
is particularly good - IMO the sponsor should be in "signed_by",
and the t2u information should be relegated to a special field,
in accordance with UDD's usual principles of providing cooked,
directly useable data.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.