Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7rBH-007thO-Jh for pgsql-hackers@arkaria.postgresql.org; Fri, 17 May 2024 06:35:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s7rBG-006d2a-Rw for pgsql-hackers@arkaria.postgresql.org; Fri, 17 May 2024 06:35:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7rBF-006d2Q-B2 for pgsql-hackers@lists.postgresql.org; Fri, 17 May 2024 06:35:02 +0000 Received: from wfout5-smtp.messagingengine.com ([64.147.123.148]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7rB6-000fCr-FO for pgsql-hackers@lists.postgresql.org; Fri, 17 May 2024 06:35:00 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfout.west.internal (Postfix) with ESMTP id 604A21C00098; Fri, 17 May 2024 02:34:49 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 17 May 2024 02:34:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1715927688; x=1716014088; bh=lWb28wCIr9JK0zKFNwiuKhPUzEcvfoNGVcpDkf5QF/c=; b= TDEnBOvCZqN3DrT/6OHE9hBGC0sz2YmdiNTJWVo8C6wCr1gGELLkhc/8TqtRCILQ 6/rtCTWA06ZIWUwPVt9I//0brzINbAe+UMWV+6Ysqky2BlmEWYaN2eLusK1TyZ3q swJ6TjZvyu875nT4nWIG/hhcobyKl/fPYxi8pc7gKkv9bRC51QEOrpR8TgoAOJdo KK/DdqOR8YhBp4/nMAOV/M4B0Nn3ZS6x5ZNFQ5G9HtbAYFjG1o7eRFA0KF5JBsTV dPyIbFo3bYwtTjijbsX4EiwOC26gvx+4e4PKe92DwGaAbe1WlnVWk1RaoNTF0wPQ B64hlwyJUA8749X2Kfu4fg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1715927688; x= 1716014088; bh=lWb28wCIr9JK0zKFNwiuKhPUzEcvfoNGVcpDkf5QF/c=; b=Y 3qgW2Yg3Gcp72W1HZWf1cbEbDGN8EvGqa0KKr1H7dO6GJF6V1/Ub1wcWfo/JVT+p HehB7WDKVb3gguS9RJ2QigbzwF2c6RZJmJIxsmB+Wzf52C4tIQuhnl5z6UqDQyNa Eai3CTt35AsDkA9LPlZ8sCodatcGbd77784STwzmQtgE9nfUJsHFydRJwnex0DRq l5soEo78mg3LYPRdP15jLDy+cFnLXlPapwVydI9WrPgLIJtFg5aI03e86MStjw0g tl6g8IKaaNj1RtROLa8KEdyXyalA2OOt8tL6IVqiNh0laR//z5XpiF1Go45ovxOs vrOTk6cThsgFrHHS2Dpyg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdehfedggeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhgqe enucggtffrrghtthgvrhhnpeehiedvhfeuhfeugefgfeehgeejtdevuefhtefhueefvddu gfdtueehgfefudfhffenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 17 May 2024 02:34:47 -0400 (EDT) Message-ID: Date: Fri, 17 May 2024 08:34:46 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Ignore Visual Studio's Temp Files While Working with PG on Windows To: Yasir , PostgreSQL Hackers References: Content-Language: en-US From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 17.05.24 08:09, Yasir wrote: > I have been playing with PG on the Windows platform recently. An > annoying thing I faced is that a lot of Visual Studio's temp files kept > appearing in git changed files. Therefore, I am submitting this very > trivial patch to ignore these temp files. Our general recommendation is that you put such things into your personal global git ignore file. For example, I have in ~/.gitconfig [core] excludesFile = ~/.gitexcludes and then in ~/.gitexcludes I have various ignores that are specific to my local tooling. That way we don't have to maintain ignore lists for all the tools in the world in the PostgreSQL source tree.