Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hcY4w-0005GH-Px for pgsql-admin@arkaria.postgresql.org; Sun, 16 Jun 2019 16:32:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hcY4v-0007dr-MC for pgsql-admin@arkaria.postgresql.org; Sun, 16 Jun 2019 16:32:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hcY4v-0007dd-4z for pgsql-admin@lists.postgresql.org; Sun, 16 Jun 2019 16:32:25 +0000 Received: from mail-qt1-x832.google.com ([2607:f8b0:4864:20::832]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hcY4s-0007cV-7n for pgsql-admin@lists.postgresql.org; Sun, 16 Jun 2019 16:32:24 +0000 Received: by mail-qt1-x832.google.com with SMTP id h21so8081739qtn.13 for ; Sun, 16 Jun 2019 09:32:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=glhgMP0wdr8+R64iTTXA/4QD+z2zK8HTj/kNhUNp3tQ=; b=chks0QuK70W4g+bbpzecwHhBTQNFgrBBJ30dI4wj0AQHgdrno0L4ZNttDGh3CcZK/B kVywlNgmWvMbVYW67CXz5H3irweQX/P4JSl3xhQ+ExvnENux7cd9ewixFQEiH8QrwptF M+kHa8H5E4Dd3MqDAY0h2PQxFiYIl4iX/H9XVFZ1XzSKN9HS3hddRDpPr+8LD0kwqIvE sgkoCLTyzAizRyICbIE0hYf9XYUjmE14lMCmM3PzeJloJ5Z9vYpHugUt9TBxRSuE1I29 cVRKqtuv0lThC1Z5yAzm+pkinBmMYdgHlcgXwMMAbAoQBSiACS5kmor61bja1EmYqaXC EYQA== 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:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=glhgMP0wdr8+R64iTTXA/4QD+z2zK8HTj/kNhUNp3tQ=; b=B/U/JeyPduUOkn44c8FpyINRGfdyCdBqhJI22bOEZqQhTYPA3CfKQ/+SwH6yD3hlst LDdMJEXVi56QzzDngvn9jmtnYmgp6MTUG09JCOZUpoBLNeUuzxdyIHEzyW0g4P2v3xvH k0tbVgSwVEKm6nvMfNMJ8+cOoz1avMrXTwjcjMq15GjZqgTOzdOuQSOv6x6cDDGOQRNH QfGuqLeWHCopXlPUZGLixsGQKicL8b0aFIPR9mz8Cw6RJnqLTEfBELnzL5psvGuNOpUJ 8ltZUkIbW9d5o4hkmWzVMgvblbarNt3Eju6FC3OQbadsA6gVYpjKP1nxFzikB8i33Ovq fGfA== X-Gm-Message-State: APjAAAU7A6tDJZFSWYdDqcv6/MVfWdMssNrMZepoTw/siTz8RewBj61m pJyqEGWLWaHOxf0TVcaWsna0ng== X-Google-Smtp-Source: APXvYqyUYKAK4/9ZN5g9Isws/1Lrb+iB0ONqprdJKBSrGdqxczbmatpElw259A1YVHvVQspGMzgTug== X-Received: by 2002:aed:3f10:: with SMTP id p16mr25403975qtf.110.1560702741313; Sun, 16 Jun 2019 09:32:21 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([179.56.48.227]) by smtp.gmail.com with ESMTPSA id j19sm2663556qtq.94.2019.06.16.09.32.20 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Sun, 16 Jun 2019 09:32:20 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 1A7E4120870; Sun, 16 Jun 2019 12:32:19 -0400 (-04) Date: Sun, 16 Jun 2019 12:32:19 -0400 From: Alvaro Herrera To: Avin Kavish Cc: pgsql-admin@lists.postgresql.org Subject: Re: I want the elephant back Message-ID: <20190616163219.GA20530@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Jun-16, Avin Kavish wrote: > The elephant on the header has been replaced by a generic flat logo with no > character which I'm fine with as that seems to be the trend these days but > I would like the option to get the elephant back for myself. In fact, I'd > like the entire two-tone header back please. That used to be a defining > character of the design that set it apart from InstaBookUberMail and made > me feel like I was using a tool designed for intellectuals, but now my > bubble is burst. Please send help. #saveTheElephant > If I need to fork it to save it, so be it, where's the repo? One little > switch in File -> Preferences -> Theme is enough. It's not clear, from this report, what product you are talking about. You need to be more explicit. The PostgreSQL core project proper does not have any logo that has changed recently. Maybe you're talking about a side project such as pgAdmin? If so, this report belongs elsewhere. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services