Git development
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Junio C Hamano" <gitster@pobox.com>,
	"GIT Mailing-list" <git@vger.kernel.org>,
	"Uwe Kleine-König" <uwe@kleine-koenig.org>
Subject: Re: sparse job, was Re: [PATCH] test-xml-encode: fix sparse NULL pointer warnings
Date: Mon, 28 Jan 2019 17:44:26 -0800	[thread overview]
Message-ID: <20190129014426.GC7268@google.com> (raw)
In-Reply-To: <a6b689da-b002-0aa2-e9d6-755d004bc320@ramsayjones.plus.com>

(+cc: Uwe Kleine-König, maintainer of the sparse package in Debian)
Hi,

Ramsay Jones wrote[1]:

> Hmm, I've never built an Ubuntu package before, so I don't know
> exactly what would be required (spec file etc.) to create a PPA.
> But I suspect you are not talking about doing that, right?

Ubuntu uses the sparse packaging as is from Debian, so no PPA should
be needed.  I've sent https://bugs.debian.org/920776 to get the
package updated in Debian.  If all is well, it should go smoothly.

Thanks,
Jonathan

[1] https://public-inbox.org/git/ef5a8623-e5e6-5cc8-5178-0afce7b5499e@ramsayjones.plus.com/

  parent reply	other threads:[~2019-01-29  1:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 21:03 [PATCH] test-xml-encode: fix sparse NULL pointer warnings Ramsay Jones
2019-01-28 16:10 ` sparse job, was " Johannes Schindelin
2019-01-28 20:13   ` Ramsay Jones
2019-01-28 22:34     ` Johannes Schindelin
2019-01-29  0:02       ` Ramsay Jones
2019-01-29  1:44     ` Jonathan Nieder [this message]
2019-01-29  1:52     ` Luc Van Oostenryck
2019-01-29  2:23       ` Ramsay Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190129014426.GC7268@google.com \
    --to=jrnieder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ramsay@ramsayjones.plus.com \
    --cc=uwe@kleine-koenig.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox