Hi Tony,

Thank you, this is exactly what I wanted. I can see the move below in the history.

c:\Python\pythonnet>git clone https://github.com/pythonnet/pythonnet Cloning into 'pythonnet'... remote: Counting objects: 3000, done. remote: Total 3000 (delta 0), reused 0 (delta 0), pack-reused 2999 Receiving objects: 100% (3000/3000), 2.56 MiB | 1.58 MiB/s, done. Resolving deltas: 100% (2075/2075), done. Checking connectivity... done.

c:\Python\pythonnet>cd pythonnet

c:\Python\pythonnet\pythonnet>git log --follow src/embed_tests/pyimport.cs commit f41cf630e28858a9fc22766b5182fdb1253c94d9 Author: Victor Uriarte Date: Sun Apr 17 01:04:52 2016 -0700

Format, white-space .cs files

commit d4882688df6cbd2454f344da6a2a573e2575a7e0 Author: David Anthoff Date: Fri Apr 11 14:34:26 2014 -0700

Move everything from pythonnet folder to root folder

Main reason is that setup.py should be in root.

commit 217bb4847d3c181b8251e84d7eab26dba1341655 Author: Barton Cline Date: Mon Apr 8 09:36:23 2013 +0000

# BUGFIX: Accommodate new output path (x86 vs. x64) #

commit de5492d145195a23239cdd3c553fd1314b67b846 Author: Barton Cline Date: Mon Apr 8 08:55:03 2013 +0000

# FIXED: .sln and .csproj file configurations x86/x64 Mono/Win Debug/Release all reflected throughout # # Added Conditional Reference <Choose> <When> elements to Python.Runtime.csp roj => building for Mono on Windows # # Added Required reference assemblies => building for Mono on Windows #

# R# Cleanup on pyimport.cs # # Remove reference to the Python.Runtime project from Console.csproj #

# BUGFIX: TARGET_PLATFORM==x86 in buildclrmodule.bat #

commit dc7614d227f77ae2db7071651d3d23b11bddc239 Author: Barton Cline Date: Mon Jan 23 07:27:32 2012 +0000

# Slashes in path are unix/linux (tested on Windows) # # Target Framework is 3.5 # # nUnit version is 2.5.9.10348 # # nUnit state storage added #

commit 4f790456e751ede65fc5ead8a9aa609a7f66b247 Author: Barton Cline Date: Thu Oct 7 08:16:52 2010 +0000

I've been adding pieces to the UnitTest classes. This addition tests embedding nested imports. The Python parts are in the te sts directory and the managed parts are in the embed_tests directroy as are the nunit parts. This test also demonstrates some neat tricks that can be done when embedding a python interpreter in managed code by using reflection to call inte rnal members of the Python.Runtime. The project settings file is VS2008, which m eans that it's probably time to go ahead and bring the rest of the project files up to a more recent version of Visual Studio.

c:\Python\pythonnet\pythonnet>

On Thu, Sep 8, 2016 at 11:03 AM, Tony Roberts tony@pyxll.com wrote:

Some files were moved some time after being imported from svn. You need to use --follow to follow renames/moves, i.e:

git log --follow src/embed_tests/pyimport.cs

All commits from svn were imported into git (and are still there). The one you mention is here: https://github.com/pythonnet/pythonnet/commit/ 217bb4847d3c181b8251e84d7eab26dba1341655

On Thu, Sep 8, 2016 at 4:18 PM Denis Akhiyarov denis.akhiyarov@gmail.com wrote:

...

It happened to me multiple times that the author of particular piece of code was needed to be known.

But in the latest pythonnet repository on github we have seem to lost some of this history when transitioning from sourceforge.

Are there any git experts, who know how to rebuild the history to include some missing commits?

Here is a quick example. Based on a bug report [1] I'm looking at lost history [2] of this C# file in the master branch [3]:

[1] https://github.com/pythonnet/pythonnet/issues/262

[2] https://github.com/pythonnet/pythonnet-rawsvnmig/ blob/master/pythonnet/src/embed_tests/pyimport.cs

[3] https://github.com/pythonnet/pythonnet/blob/master/src/embed_tests/ pyimport.cs

---

Python.NET mailing list - PythonDotNet@python.org https://mail.python.org/mailman/listinfo/pythondotnet

---

Python.NET mailing list - PythonDotNet@python.org https://mail.python.org/mailman/listinfo/pythondotnet