From owner-freebsd-amd64@freebsd.org Sat Apr 20 15:13:18 2019 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9CBE4158FFF4 for ; Sat, 20 Apr 2019 15:13:18 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05965944E7 for ; Sat, 20 Apr 2019 15:13:18 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x336.google.com with SMTP id w15so9439822wmc.3 for ; Sat, 20 Apr 2019 08:13:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=tQqIsMNpowvq/ydD5S8VTEKDR2oYgqtwhXqjyKms3D4=; b=PB/6TejtytF3XBusVTjMsHTCOO8BDuabXjNcLeManpbXrG2c5FUdrFd8XhB/Y7tTrq TBpHyHBTh4GFJlIt6zM1nr4jMN6iSNwaSgeKN8LU5dEdkCo96aoQh/S8MpHEO6vPlyyF mI+8pLpVS1/B1rzfpZxfiG3W3UtCIoYen7vGWt1zUOZiDfCrKmSR+7ZduaDsGKydXc7B N4GOTVHy1nY4d7Xe+qjh+VHXTgkq8kGqgjdzEeoft0BiSU8pcxaAinLg7xzwkwWMli+b SvTso5o3uqex1gmKzlFxKulOCo0s9RdRNbaitO561Ngl4IBREJ8fU0H4Ychui+cunRfJ uP2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=tQqIsMNpowvq/ydD5S8VTEKDR2oYgqtwhXqjyKms3D4=; b=tzFdtgqEWqTUC1tPFcPWGhB8gfIKNbRWQWsFvdOD6guWrMnWKNDGz/Hgev68OmhvUr q1sBPqo4AZVBIIGvb/nN6cGa35FDq7NbJnaw/Hhx/b/I9t1gvUy6aHe0pZZyN7FCKLmP HVN7woqyzHOwroX//NipwwzHpW0gN1OWVE8yYqlQ7GxQMKCWVsvo6OqrfFYZOyOeFAzd OuiBQjUmkGyI5Q62JmMW7Q4LeuR8qm5vYFJIllISQ5ekurUFUunj8i4zKjIFyjq5WKkr QRkzw6LVHhfA4xerGDFF0h+iQvvNX7/OCdPix4YIQW4FVXRN2pFvXNL9P15oMHyjhPoq Cq3w== X-Gm-Message-State: APjAAAW8vRPTrT13JOxXvNLHamVEJR85LS26CMP38tVKzUEZsUovAlIf NlS1/8JZaflpHNiUxKJnuaDMOoax X-Google-Smtp-Source: APXvYqxfXo4tsTcHrZu3z4UmOLuxDVHdcgB5mhTrnL91twKyax/e/blolTlFS/XIocjLorQnAqy/iw== X-Received: by 2002:a1c:720a:: with SMTP id n10mr6110258wmc.107.1555773195788; Sat, 20 Apr 2019 08:13:15 -0700 (PDT) Received: from ernst.home (p5B3BEDB7.dip0.t-ipconnect.de. [91.59.237.183]) by smtp.gmail.com with ESMTPSA id r16sm6756254wrx.37.2019.04.20.08.13.14 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 20 Apr 2019 08:13:14 -0700 (PDT) Date: Sat, 20 Apr 2019 17:13:13 +0200 From: Gary Jennejohn To: freebsd-amd64@freebsd.org Subject: Re: Contacting mate-media maintainer, eg. gnome@freebsd.org not responsive? Message-ID: <20190420171313.41c04f97@ernst.home> In-Reply-To: <8a01866b-cfaa-f3fd-1c6e-014ed7d5be94@bege.email> References: <8a01866b-cfaa-f3fd-1c6e-014ed7d5be94@bege.email> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 05965944E7 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.984,0] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Apr 2019 15:13:18 -0000 On Sat, 20 Apr 2019 14:29:16 +0200 Georg Bege wrote: > Hello people, > > what would I need to do if I wanted to contact a maintainer which is not available/unresponsive? > Who's maintaining the mate packages, is gnome@ a generic alias? > I tried to come in contact some months ago but failed... > It would be better to send this inquiry to ports@. amd64@ has nothing to do with maintaining ports. -- Gary Jennejohn