A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-April/118383.html below:

[Python-Dev] .{git,bzr}ignore in cpython HG repo

[Python-Dev] .{git,bzr}ignore in cpython HG repoGuido van Rossum guido at python.org
Mon Apr 2 00:52:03 CEST 2012
On Fri, Mar 30, 2012 at 8:00 AM, Matěj Cepl <mcepl at redhat.com> wrote:
> Why does HG cpython repo contains .{bzr,git}ignore at all?

So that when people switch between repo software the set of ignored
files remains constant. While the "official" repo isn't going to
switch any time soon, various developers for various reasons prefer
different repo software and the tools for copying repos work well
enough that people actually do this, for various workflow purposes. As
long as patches eventually find their way back into the central Hg
repo I have no problem in it.

> IMHO, all .*ignore files should be strictly repository dependent and they
> should not be mixed together.

No, because then everybody who copies a repo to a different tool would
have to start over from scratch.

> It is even worse, that (understandingly) .{bzr,git}ignore are apparently
> poorly maintained, so in order to get an equivalent of .hgignore in
> .gitignore, one has to apply the attached patch.

Please file a bug to get this reviewed and checked in.

-- 
--Guido van Rossum (python.org/~guido)
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4