git@vger.kernel.org mailing list mirror (one of many)
 help / color / Atom feed
From: Todd Zullinger <tmz@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2019, #03; Wed, 13)
Date: Thu, 14 Feb 2019 01:49:56 -0500
Message-ID: <20190214064956.GE16125@zaya.teonanacatl.net> (raw)
In-Reply-To: <20190214055315.GK20578@sigill.intra.peff.net>

Jeff King wrote:
> Yeah, I do have the feeling that not many people really exercise our -rc
> candidates. I'm not sure how to improve that. We could try to push
> packagers to make them available (and I think Jonathan already does for
> Debian's "experimental" track).

Similarly, I try to make them available in Fedora's rawhide
channel (as well as less officially as builds for current
stable Fedora and RHEL/CentOS releases¹).  I don't have a
good sense of how many git users that reaches, but I haven't
had many (or perhaps any?) bug reports from the -rc
packages.

I typically wait for -rc1 to push to rawhide, just to give a
little time to weed out the early issues.  I'd make the
Fedora QA folks mad if I pushed a git update that caused
them too much grief.

Thankfully, I can't recall ever having such a problem
(certainly nothing that most users of git would run into).

> But ultimately I think it is not a packaging/availability question, but
> just that most people do not bother until there is a real release.

Indeed.

¹ Those "less official" packages are:
  https://copr.fedorainfracloud.org/coprs/g/git-maint/git/ &
  https://copr.fedorainfracloud.org/coprs/tmz/git/

-- 
Todd

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  3:33 Junio C Hamano
2019-02-14  3:59 ` Jeff King
2019-02-14  5:49   ` Junio C Hamano
2019-02-14  5:53     ` Jeff King
2019-02-14  6:49       ` Todd Zullinger [this message]
2019-02-14  6:54         ` Jeff King
2019-02-14 20:10 ` Jonathan Tan
2019-02-14 20:47   ` Junio C Hamano

Reply instructions:

You may reply publically 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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=20190214064956.GE16125@zaya.teonanacatl.net \
    --to=tmz@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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

git@vger.kernel.org mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/
       or Tor2web: https://www.tor2web.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox