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/2014-December/137383.html below:

[Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

[Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and GithubMarkus Unterwaditzer markus at unterwaditzer.net
Mon Dec 1 02:27:10 CET 2014
On 1 December 2014 01:17:02 CET, Ben Finney <ben+python at benfinney.id.au> wrote:
>Donald Stufft <donald at stufft.io> writes:
>
>> I have never heard of git losing history.
>
>In my experience talking with Git users about this problem, that
>depends
>on a very narrow definition of “losing history”.
>
>Git encourages re-writing, and thereby losing prior versions of, the
>history of a branch. The commit information remains, but the history of
>how they link together is lost. That is a loss of information, which is
>not the case in the absence of such history re-writing.

"Losing data" is generally used in the sense that either the application or the filesystem accidentally deletes or overwrites data without the user's consent or knownledge. Rewriting and deleting (not "losing") history in git is explicitly done by the user, encouraged or not.

-- Markus
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