cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: ANNOUNCE: cluster.git repository moved to fedorahosted.org (UPDATE)
Date: Wed, 30 Jul 2008 06:38:25 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0807300635380.14806@trider-g7> (raw)
In-Reply-To: <Pine.LNX.4.64.0807292158040.14806@trider-g7>

On Tue, 29 Jul 2008, Fabio M. Di Nitto wrote:

> - emails to cluster-cvs at sources.redhat.com are temporary disabled.
>  cluster-devel at redhat.com is the only mailing list receiving
>  notifications. This will change soon in such a way that _only_
>  cluster-cvs will see commit emails.

This issue has been fixed now. All emails should go to cluster-cvs mailing 
list only.

A problem was found with the annotated tag generation that prevented 
emails from being generated.

The following tags:

  * [new tag]         cman_2_0_86 -> cman_2_0_86
  * [new tag]         cmirror-kernel_0_1_11 -> cmirror-kernel_0_1_11
  * [new tag]         cmirror-kernel_0_1_12 -> cmirror-kernel_0_1_12
  * [new tag]         cmirror-kernel_0_1_13 -> cmirror-kernel_0_1_13
  * [new tag]         cmirror_1_1_20 -> cmirror_1_1_20
  * [new tag]         cmirror_1_1_21 -> cmirror_1_1_21
  * [new tag]         cmirror_1_1_22 -> cmirror_1_1_22
  * [new tag]         fence_1_32_62 -> fence_1_32_62
  * [new tag]         fence_1_32_63 -> fence_1_32_63

did not hit any mailing list.

The problem has been solved now by enforcing email filters only on 
branches and tracking branches.

Fabio

--
I'm going to make him an offer he can't refuse.



      reply	other threads:[~2008-07-30  4:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 20:09 [Cluster-devel] ANNOUNCE: cluster.git repository moved to fedorahosted.org Fabio M. Di Nitto
2008-07-30  4:38 ` Fabio M. Di Nitto [this message]

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=Pine.LNX.4.64.0807300635380.14806@trider-g7 \
    --to=fdinitto@redhat.com \
    /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).