git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: funeeldy <Marlene_Cote@affirmednetworks.com>
To: git@vger.kernel.org
Subject: git issues/bugs - is there an alert process?
Date: Mon, 23 May 2011 10:44:13 -0700 (PDT)	[thread overview]
Message-ID: <1306172653284-6395510.post@n2.nabble.com> (raw)

Is there any way for me to sign up to get alerts for serious bugs discovered
in a version of git?
Evidently, there have been some pretty serious bugs in version 1.7.3 that I
didn't even know about, and they may have caused problems for my developers. 
with more and more enterprise use of git, we really need to be able to
support it in a more robust manner.
Thanks
Marlene

--
View this message in context: http://git.661346.n2.nabble.com/git-issues-bugs-is-there-an-alert-process-tp6395510p6395510.html
Sent from the git mailing list archive at Nabble.com.

             reply	other threads:[~2011-05-23 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 17:44 funeeldy [this message]
2011-05-23 21:21 ` git issues/bugs - is there an alert process? Jeff King
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=1306172653284-6395510.post@n2.nabble.com \
    --to=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).