From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82063 invoked by alias); 16 Feb 2017 08:38:24 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 81964 invoked by uid 89); 16 Feb 2017 08:38:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=frank, Frank, fwd, hosting X-HELO: mail-wm0-f47.google.com Received: from mail-wm0-f47.google.com (HELO mail-wm0-f47.google.com) (74.125.82.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 16 Feb 2017 08:38:13 +0000 Received: by mail-wm0-f47.google.com with SMTP id c85so60445620wmi.1 for ; Thu, 16 Feb 2017 00:38:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SntjU6ZuU0SWRwQfy6/pgvOTVxQoQhC5pG2xx3GN3v4=; b=jYeyKduDTVAjlbk0DiTve4dKjeSgEppyqbU6hBVkg9cMhBZxNbWzPvZVfa7LSxzGTJ FLXQ2R/Vlx2M8WG5dxJsxQST3CevRlCRwfFEx4tJe9V5RpnZ9T0KkuId20AlpqlqA/Hu JgWuEGL4fWch3H97qkV5sSkPsNJwKEVA7evWFKjaNM8wZDZx8vDMHQOfL3zVW5tEzMFp VqdJL2LW9cQLpm7jzea4Mm6BP2byHTb4/SCDBoOFi+1P3FblLcYSl8eyEFk7Axa/+e/U W/ITXozAyX5TSwKW/7oFczfCrA2KuWSWefPku1oVnVmafELOeL8C8XRGWLh/ySKw9uk4 PJwA== X-Gm-Message-State: AMke39mlRFXbUa1pNZ0ZFpODc8SbhecFOw/1WBalHtrP2FdcF+VAiNuvLmKr+xYyeUxvbA== X-Received: by 10.28.226.67 with SMTP id z64mr10797651wmg.137.1487234290592; Thu, 16 Feb 2017 00:38:10 -0800 (PST) Received: from mail-wr0-f182.google.com (mail-wr0-f182.google.com. [209.85.128.182]) by smtp.gmail.com with ESMTPSA id n18sm7887806wra.64.2017.02.16.00.38.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 00:38:10 -0800 (PST) Received: by mail-wr0-f182.google.com with SMTP id 89so1945492wrr.3 for ; Thu, 16 Feb 2017 00:38:10 -0800 (PST) X-Received: by 10.223.143.45 with SMTP id p42mr985705wrb.120.1487234290301; Thu, 16 Feb 2017 00:38:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.139.80 with HTTP; Thu, 16 Feb 2017 00:38:09 -0800 (PST) In-Reply-To: <20170209224434.GM41423@elastic.org> References: <20170204225408.GF41423@elastic.org> <20170206160126.GH41423@elastic.org> <20170206210512.GJ41423@elastic.org> <20170209224434.GM41423@elastic.org> From: Ivo Raisr Date: Thu, 16 Feb 2017 08:38:00 -0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Fwd: hosting Valgrind repository on sourceware.org To: "Frank Ch. Eigler" Cc: overseers@sourceware.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2017-q1/txt/msg00085.txt.bz2 Hi Frank, I would like confirm with you about possibility of sending notifications about pushed commits to Valgrind repo. I think for example both glibc and gdb have setup post-receive hook so their alias gets an email when a push happens. Is that something we can (re)use for Valgrind as well? However we would like to get notification only when a push was done for master branch; for example as discussed here: http://stackoverflow.com/questions/7351551/writing-a-git-post-receive-hook-to-deal-with-a-specific-branch Thank you, I.