delta/libgit2.git/src/push.c, branch ethomson/proxy github.com: libgit2/libgit2.git remote: store the connection data in a private struct 2018-09-07T10:37:22+00:00 Etienne Samson samson.etienne@gmail.com 2018-09-07T10:36:15+00:00 1c176883880c4f487597074c70f9bb6f96198737 This makes it easier to pass connection-related options around (proxy & custom headers for now). This fixes a bug in git_push_finish, which didn't reuse the provided proxy if the connection closed between the call to `git_remote_push` and the finish step. 
This makes it easier to pass connection-related options around (proxy &
custom headers for now).

This fixes a bug in git_push_finish, which didn't reuse the provided
proxy if the connection closed between the call to `git_remote_push` and
the finish step.
 refspec: rename `git_refspec__free` to `git_refspec__dispose` 2018-06-29T09:45:15+00:00 Patrick Steinhardt ps@pks.im 2018-06-29T09:45:15+00:00 af3088e4642a0babb1cd26f5ed143f087f5a71f8 Since commit 630a67366 (refspec: add public parsing api, 2018-02-07), we now have two functions `git_refspec_free` and `git_refspec__free`. The difference is that the first one will free the structure itself, while the second one will only free the structure's contents. Use our new `dispose` naming pattern for the latter function to help avoid confusion. 
Since commit 630a67366 (refspec: add public parsing api, 2018-02-07), we
now have two functions `git_refspec_free` and `git_refspec__free`. The
difference is that the first one will free the structure itself, while
the second one will only free the structure's contents. Use our new
`dispose` naming pattern for the latter function to help avoid
confusion.
Convert usage of `git_buf_free` to new `git_buf_dispose` 2018-06-10T17:34:37+00:00 Patrick Steinhardt ps@pks.im 2018-02-08T11:14:48+00:00 ecf4f33a4e327a91496f72816f9f02d923e5af05 






Merge pull request #4028 from chescock/improve-local-fetch
2017-12-30T19:07:03+00:00

Edward Thomson
ethomson@edwardthomson.com

2017-12-30T19:07:03+00:00

8cdf439b7714449eaddf5564933cd2fee1fc02cb

Transfer fewer objects on push and local fetch




Transfer fewer objects on push and local fetch






Clear the remote_ref_name buffer in git_push_update_tips()
2017-09-11T18:34:41+00:00

Slava Karpenko
slavikus@gmail.com

2017-09-11T18:34:41+00:00

b34fc3fdf6071365cb5585ed929bd3dc714b67c0

If fetch_spec was a non-pattern, and it is not the first iteration of push_status vector, then git_refspec_transform would result in the new value appended via git_buf_puts to the previous iteration value.

Forcibly clearing the buffer on each iteration to prevent this behavior.





If fetch_spec was a non-pattern, and it is not the first iteration of push_status vector, then git_refspec_transform would result in the new value appended via git_buf_puts to the previous iteration value.

Forcibly clearing the buffer on each iteration to prevent this behavior.







Make sure to always include "common.h" first
2017-07-03T08:51:48+00:00

Patrick Steinhardt
ps@pks.im

2017-06-30T11:39:01+00:00

0c7f49dd4316b332f30b4ea72a657bace41e1245

Next to including several files, our "common.h" header also declares
various macros which are then used throughout the project. As such, we
have to make sure to always include this file first in all
implementation files. Otherwise, we might encounter problems or even
silent behavioural differences due to macros or defines not being
defined as they should be. So in fact, our header and implementation
files should make sure to always include "common.h" first.

This commit does so by establishing a common include pattern. Header
files inside of "src" will now always include "common.h" as its first
other file, separated by a newline from all the other includes to make
it stand out as special. There are two cases for the implementation
files. If they do have a matching header file, they will always include
this one first, leading to "common.h" being transitively included as
first file. If they do not have a matching header file, they instead
include "common.h" as first file themselves.

This fixes the outlined problems and will become our standard practice
for header and source files inside of the "src/" from now on.





Next to including several files, our "common.h" header also declares
various macros which are then used throughout the project. As such, we
have to make sure to always include this file first in all
implementation files. Otherwise, we might encounter problems or even
silent behavioural differences due to macros or defines not being
defined as they should be. So in fact, our header and implementation
files should make sure to always include "common.h" first.

This commit does so by establishing a common include pattern. Header
files inside of "src" will now always include "common.h" as its first
other file, separated by a newline from all the other includes to make
it stand out as special. There are two cases for the implementation
files. If they do have a matching header file, they will always include
this one first, leading to "common.h" being transitively included as
first file. If they do not have a matching header file, they instead
include "common.h" as first file themselves.

This fixes the outlined problems and will become our standard practice
for header and source files inside of the "src/" from now on.







giterr_set: consistent error messages
2016-12-29T12:26:03+00:00

Edward Thomson
ethomson@github.com

2016-12-29T12:25:15+00:00

909d5494368a00809bc42f4780e86f4dd66e4422

Error messages should be sentence fragments, and therefore:

1. Should not begin with a capital letter,
2. Should not conclude with punctuation, and
3. Should not end a sentence and begin a new one





Error messages should be sentence fragments, and therefore:

1. Should not begin with a capital letter,
2. Should not conclude with punctuation, and
3. Should not end a sentence and begin a new one







Use git_packbuilder_insert_walk in queue_objects.
2016-12-20T19:23:29+00:00

Chris Hescock
chescock@vistaprint.com

2016-12-09T22:11:58+00:00

2dcfe51de1cec11764ba88edd8eb585fa0fc02d4












proxy: ask the user for credentials if necessary
2016-04-19T11:54:19+00:00

Carlos Martín Nieto
cmn@dwim.me

2015-05-07T10:57:56+00:00

07bd3e57d9a9930727695be690c8757f79117d45












tree: re-use the id and filename in the odb object
2016-03-20T10:00:12+00:00

Carlos Martín Nieto
cmn@dwim.me

2016-03-20T10:00:12+00:00

60a194aa86d54ffb55c1abff8d0ef05647f936e8

Instead of copying over the data into the individual entries, point to
the originals, which are already in a format we can use.





Instead of copying over the data into the individual entries, point to
the originals, which are already in a format we can use.