<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/python-packages/gitpython.git/git/test/test_index.py, branch 1.0.2</title>
<subtitle>github.com: gitpython-developers/GitPython.git
</subtitle>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/'/>
<entry>
<title>fix(compat): make test work with git &gt;= 2.5</title>
<updated>2015-08-29T14:25:40+00:00</updated>
<author>
<name>Sebastian Thiel</name>
<email>byronimo@gmail.com</email>
</author>
<published>2015-08-29T14:25:40+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=7f8d9ca08352a28cba3b01e4340a24edc33e13e8'/>
<id>7f8d9ca08352a28cba3b01e4340a24edc33e13e8</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(test_index): fix encoding</title>
<updated>2015-08-17T20:39:13+00:00</updated>
<author>
<name>Sebastian Thiel</name>
<email>byronimo@gmail.com</email>
</author>
<published>2015-08-17T20:39:13+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=c8b837923d506e265ff8bb79af61c0d86e7d5b2e'/>
<id>c8b837923d506e265ff8bb79af61c0d86e7d5b2e</id>
<content type='text'>
I really never want to touch python again, and never deal with
py2/3 unicode handling anymore.
By now, it seems pretty much anything is better.
Is python to be blamed for it entirely ?
Probably not, but there are better alternatives.
Nim ? Rust ? Ruby ?
Totally
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I really never want to touch python again, and never deal with
py2/3 unicode handling anymore.
By now, it seems pretty much anything is better.
Is python to be blamed for it entirely ?
Probably not, but there are better alternatives.
Nim ? Rust ? Ruby ?
Totally
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(index):allow adding non-unicode paths to index</title>
<updated>2015-07-29T16:29:03+00:00</updated>
<author>
<name>Sebastian Thiel</name>
<email>byronimo@gmail.com</email>
</author>
<published>2015-07-29T16:29:03+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=7ab12b403207bb46199f46d5aaa72d3e82a3080d'/>
<id>7ab12b403207bb46199f46d5aaa72d3e82a3080d</id>
<content type='text'>
This issue only surfaced in python 2, in case paths containing unicode
characters were not actual unicode objects.

In python 3, this was never the issue.

Closes #331
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This issue only surfaced in python 2, in case paths containing unicode
characters were not actual unicode objects.

In python 3, this was never the issue.

Closes #331
</pre>
</div>
</content>
</entry>
<entry>
<title>added tests for commits with dates</title>
<updated>2015-07-17T16:48:46+00:00</updated>
<author>
<name>avi</name>
<email>hi@avi.im</email>
</author>
<published>2015-07-17T16:48:46+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=e3068025b64bee24efc1063aba5138708737c158'/>
<id>e3068025b64bee24efc1063aba5138708737c158</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(index): handle adding symlinks to dirs</title>
<updated>2015-06-26T07:58:47+00:00</updated>
<author>
<name>Sebastian Thiel</name>
<email>byronimo@gmail.com</email>
</author>
<published>2015-06-26T07:58:47+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=cfc70fe92d42a853d4171943bde90d86061e3f3a'/>
<id>cfc70fe92d42a853d4171943bde90d86061e3f3a</id>
<content type='text'>
When expanding directories, check if it is a symlink and don't expand
them at all.

Previously, we followed symlinks and expanded their contents, which
could lead to weird index files.

Fixes #302
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When expanding directories, check if it is a symlink and don't expand
them at all.

Previously, we followed symlinks and expanded their contents, which
could lead to weird index files.

Fixes #302
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(index): don't write extension data by default</title>
<updated>2015-04-08T07:50:26+00:00</updated>
<author>
<name>Sebastian Thiel</name>
<email>byronimo@gmail.com</email>
</author>
<published>2015-04-08T07:50:26+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=8f043d8a1d7f4076350ff0c778bfa60f7aa2f7aa'/>
<id>8f043d8a1d7f4076350ff0c778bfa60f7aa2f7aa</id>
<content type='text'>
It turned out that the index is not actually corrupted, which is good
news. What happens is that `git` writes `TREE` extension data into the
index, which causes it to write out the given tree *as is* next time
a `git commit` is executed. When using `git add`, this extension data
is maintained automatically. However, GitPython doesn't do that ... .
Usually this is no problem at all, as you are supposed to use
`IndexFile.commit(...)` along with `IndexFile.add(...)`.

Thanks to a shortcoming in the GitPython API, the index was
automatically written out whenever files have been added, without
providing control over whether or not *extension data* will be
written along with it.

My fix consists of an additional flag in `IndexFile.add(...)`, which
causes extension data not to be written by default, so commits can be
safely done via `git commit` or `IndexFile.commit(...)`.

However, this might introduce new subtle bugs in case someone is
relying on extension data to be written. As this can be controlled
through the said flag though, a fix is easily done in that case.

Fixes #265
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It turned out that the index is not actually corrupted, which is good
news. What happens is that `git` writes `TREE` extension data into the
index, which causes it to write out the given tree *as is* next time
a `git commit` is executed. When using `git add`, this extension data
is maintained automatically. However, GitPython doesn't do that ... .
Usually this is no problem at all, as you are supposed to use
`IndexFile.commit(...)` along with `IndexFile.add(...)`.

Thanks to a shortcoming in the GitPython API, the index was
automatically written out whenever files have been added, without
providing control over whether or not *extension data* will be
written along with it.

My fix consists of an additional flag in `IndexFile.add(...)`, which
causes extension data not to be written by default, so commits can be
safely done via `git commit` or `IndexFile.commit(...)`.

However, this might introduce new subtle bugs in case someone is
relying on extension data to be written. As this can be controlled
through the said flag though, a fix is easily done in that case.

Fixes #265
</pre>
</div>
</content>
</entry>
<entry>
<title>test(index): test for #265</title>
<updated>2015-04-07T16:27:16+00:00</updated>
<author>
<name>Sebastian Thiel</name>
<email>byronimo@gmail.com</email>
</author>
<published>2015-04-07T16:27:16+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=1fd07a0a7a6300db1db8b300a3f567b31b335570'/>
<id>1fd07a0a7a6300db1db8b300a3f567b31b335570</id>
<content type='text'>
However, it doesn't reproduce on the latest version of GitPython.
Maybe it's on an older one.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
However, it doesn't reproduce on the latest version of GitPython.
Maybe it's on an older one.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fixed regression in test-suite for IndexFile</title>
<updated>2015-01-21T17:57:34+00:00</updated>
<author>
<name>Sebastian Thiel</name>
<email>byronimo@gmail.com</email>
</author>
<published>2015-01-21T17:56:29+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=d565a874f29701531ce1fc0779592838040d3edf'/>
<id>d565a874f29701531ce1fc0779592838040d3edf</id>
<content type='text'>
Previously, it checked for AssertionErrors, now we have to implement
need-unbare-repo check ourselves.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously, it checked for AssertionErrors, now we have to implement
need-unbare-repo check ourselves.
</pre>
</div>
</content>
</entry>
<entry>
<title>Improved unicode handling when using os.environ or GitConfigParser</title>
<updated>2015-01-19T17:10:16+00:00</updated>
<author>
<name>Sebastian Thiel</name>
<email>byronimo@gmail.com</email>
</author>
<published>2015-01-19T17:10:16+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=df95149198744c258ed6856044ac5e79e6b81404'/>
<id>df95149198744c258ed6856044ac5e79e6b81404</id>
<content type='text'>
Assured unicode values are supported when reading the configuration,
and when getting author/committer information from the environment.

Fixes #237
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Assured unicode values are supported when reading the configuration,
and when getting author/committer information from the environment.

Fixes #237
</pre>
</div>
</content>
</entry>
<entry>
<title>IndexFile.commit() now runs pre-commit and post-commit hooks.</title>
<updated>2015-01-12T13:55:31+00:00</updated>
<author>
<name>Sebastian Thiel</name>
<email>byronimo@gmail.com</email>
</author>
<published>2015-01-12T13:55:31+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/gitpython.git/commit/?id=e8eae18dcc360e6ab96c2291982bd4306adc01b9'/>
<id>e8eae18dcc360e6ab96c2291982bd4306adc01b9</id>
<content type='text'>
However, it does so only on posix. The test-case will run on posix only
as well.
Please note that in theory, even on windows we will attempt to run hooks,
even though I am not sure that this will actually work.

Fixes #81
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
However, it does so only on posix. The test-case will run on posix only
as well.
Please note that in theory, even on windows we will attempt to run hooks,
even though I am not sure that this will actually work.

Fixes #81
</pre>
</div>
</content>
</entry>
</feed>
