<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/libgit2.git/src, branch cmn/ssh-errors</title>
<subtitle>github.com: libgit2/libgit2.git
</subtitle>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/'/>
<entry>
<title>ssh: store error message immediately after a failed agent call</title>
<updated>2014-09-04T14:46:14+00:00</updated>
<author>
<name>Carlos Martín Nieto</name>
<email>cmn@dwim.me</email>
</author>
<published>2014-09-04T14:46:14+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=2dc399a81da0baec54da80ed90a0007fb8caed81'/>
<id>2dc399a81da0baec54da80ed90a0007fb8caed81</id>
<content type='text'>
When the call to the agent fails, we must retrieve the error message
just after the function call, as other calls may overwrite it.

As the agent authentication is the only one which has a teardown and
there does not seem to be a way to get the error message from a stored
error number, this tries to introduce some small changes to store the
error from the agent.

Clearing the error at the beginning of the loop lets us know whether the
agent has already set the libgit2 error message and we should skip it,
or if we should set it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When the call to the agent fails, we must retrieve the error message
just after the function call, as other calls may overwrite it.

As the agent authentication is the only one which has a teardown and
there does not seem to be a way to get the error message from a stored
error number, this tries to introduce some small changes to store the
error from the agent.

Clearing the error at the beginning of the loop lets us know whether the
agent has already set the libgit2 error message and we should skip it,
or if we should set it.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #2543 from libgit2/cmn/known-transports</title>
<updated>2014-09-03T10:50:44+00:00</updated>
<author>
<name>Vicent Marti</name>
<email>vicent@github.com</email>
</author>
<published>2014-09-03T10:50:44+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=89e05e2ab19ac452e84e0eaa2dfb8e07ac6839bf'/>
<id>89e05e2ab19ac452e84e0eaa2dfb8e07ac6839bf</id>
<content type='text'>
Clean up transport lookup</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Clean up transport lookup</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #2530 from libgit2/jamill/relative_gitlink</title>
<updated>2014-09-03T10:19:48+00:00</updated>
<author>
<name>Vicent Marti</name>
<email>vicent@github.com</email>
</author>
<published>2014-09-03T10:19:48+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=4c958046d3ed7f67c6dee495b8d874df9048dc55'/>
<id>4c958046d3ed7f67c6dee495b8d874df9048dc55</id>
<content type='text'>
Teach repository to use relative paths for git symbolic links</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Teach repository to use relative paths for git symbolic links</pre>
</div>
</content>
</entry>
<entry>
<title>Introduce option to use relative paths for repository work directory</title>
<updated>2014-09-03T01:07:26+00:00</updated>
<author>
<name>Jameson Miller</name>
<email>jamill@microsoft.com</email>
</author>
<published>2014-08-20T14:24:41+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=bc737620dd0d331cb80c22d074569fe29b7ab585'/>
<id>bc737620dd0d331cb80c22d074569fe29b7ab585</id>
<content type='text'>
Teach git_repository_init_ext to use relative paths for the gitlink
to the work directory. This is used when creating a sub repository
where the sub repository resides in the parent repository's
.git directory.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Teach git_repository_init_ext to use relative paths for the gitlink
to the work directory. This is used when creating a sub repository
where the sub repository resides in the parent repository's
.git directory.
</pre>
</div>
</content>
</entry>
<entry>
<title>Introduce git_path_make_relative</title>
<updated>2014-09-03T01:07:23+00:00</updated>
<author>
<name>Edward Thomson</name>
<email>ethomson@microsoft.com</email>
</author>
<published>2014-08-20T14:23:39+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=0ee9f31c3b11116ab5806ab80d03b1d37197d6ce'/>
<id>0ee9f31c3b11116ab5806ab80d03b1d37197d6ce</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Several CppCat warnings fixed</title>
<updated>2014-09-02T21:01:25+00:00</updated>
<author>
<name>Arkady Shapkin</name>
<email>arkadiy_s@inbox.ru</email>
</author>
<published>2014-09-02T21:01:25+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=5cd81bb3d88218d42dd431f2c5011dfa84c287c7'/>
<id>5cd81bb3d88218d42dd431f2c5011dfa84c287c7</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>remote: get rid of git_remote_valid_url()</title>
<updated>2014-08-31T19:50:28+00:00</updated>
<author>
<name>Carlos Martín Nieto</name>
<email>cmn@dwim.me</email>
</author>
<published>2014-08-31T15:16:40+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=ba67c0752269ba06523fe7f5fa350e6328b20241'/>
<id>ba67c0752269ba06523fe7f5fa350e6328b20241</id>
<content type='text'>
It does the same as git_remote_supported_url() but has a name which
implies we'd check the URL for correctness while we're simply looking at
the scheme and looking it up in our lists.

While here, fix up the tests so we check all the combination of what's
supported.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It does the same as git_remote_supported_url() but has a name which
implies we'd check the URL for correctness while we're simply looking at
the scheme and looking it up in our lists.

While here, fix up the tests so we check all the combination of what's
supported.
</pre>
</div>
</content>
</entry>
<entry>
<title>transport: return ENOTFOUND for HTTPS and SSH when they're not supported</title>
<updated>2014-08-31T16:01:44+00:00</updated>
<author>
<name>Carlos Martín Nieto</name>
<email>cmn@dwim.me</email>
</author>
<published>2014-08-31T15:12:45+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=bd3854a09c9bd4196cf280108d3f6286ee6de258'/>
<id>bd3854a09c9bd4196cf280108d3f6286ee6de258</id>
<content type='text'>
The previous commit makes it harder to figure out if the library was
built with support for a particular transport. Roll back some of the
changes and remove ssh:// and https:// from the list if we're being
built without support for them.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The previous commit makes it harder to figure out if the library was
built with support for a particular transport. Roll back some of the
changes and remove ssh:// and https:// from the list if we're being
built without support for them.
</pre>
</div>
</content>
</entry>
<entry>
<title>transport: distinguish between unknown and unsupported transports</title>
<updated>2014-08-31T16:01:35+00:00</updated>
<author>
<name>Carlos Martín Nieto</name>
<email>cmn@dwim.me</email>
</author>
<published>2014-08-31T14:48:41+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=dbc77850ff62b134d7fe7ab659ca2d3ef24cf556'/>
<id>dbc77850ff62b134d7fe7ab659ca2d3ef24cf556</id>
<content type='text'>
Even when built without a SSH support, we know about this transport. It
is implemented, but the current code makes us return an error message
saying it's not.

This is a leftover from the initial implementation of the transports
when there were in fact transports we knew about but were not
implemented.

Instead, let the SSH transport itself say it cannot run, the same as we
do for HTTPS.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Even when built without a SSH support, we know about this transport. It
is implemented, but the current code makes us return an error message
saying it's not.

This is a leftover from the initial implementation of the transports
when there were in fact transports we knew about but were not
implemented.

Instead, let the SSH transport itself say it cannot run, the same as we
do for HTTPS.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #2481 from libgit2/cmn/oidarray</title>
<updated>2014-08-29T16:19:56+00:00</updated>
<author>
<name>Vicent Marti</name>
<email>vicent@github.com</email>
</author>
<published>2014-08-29T16:19:56+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/libgit2.git/commit/?id=46a13f32472741f0ed66db7cb75c8cff279886ad'/>
<id>46a13f32472741f0ed66db7cb75c8cff279886ad</id>
<content type='text'>
merge: expose multiple merge bases</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
merge: expose multiple merge bases</pre>
</div>
</content>
</entry>
</feed>
