From: Jeff King <peff@peff.net>
To: funeeldy <Marlene_Cote@affirmednetworks.com>
Cc: git@vger.kernel.org
Subject: Re: git issues/bugs - is there an alert process?
Date: Mon, 23 May 2011 17:21:50 -0400 [thread overview]
Message-ID: <20110523212150.GF6281@sigill.intra.peff.net> (raw)
In-Reply-To: <1306172653284-6395510.post@n2.nabble.com>
On Mon, May 23, 2011 at 10:44:13AM -0700, funeeldy wrote:
> Is there any way for me to sign up to get alerts for serious bugs discovered
> in a version of git?
You can read the release notes; minor versions are always bugfix
releases, and important bugfixes are backported to them. If you read
only the [ANNOUNCE] messages on git@vger, you will see new releases.
I seem to recall we have an announce-only mailing list, and somebody set
up an rss feed, but I don't remember the details. Maybe somebody else
does, or you can find it via google.
-Peff
next prev parent reply other threads:[~2011-05-23 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 17:44 git issues/bugs - is there an alert process? funeeldy
2011-05-23 21:21 ` Jeff King [this message]
2011-05-23 22:21 ` Junio C Hamano
2011-05-25 13:59 ` Jakub Narebski
2011-05-25 15:14 ` Jeff King
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=20110523212150.GF6281@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Marlene_Cote@affirmednetworks.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).