delta/libgit2.git/tests/index/racy.c, branch ethomson/https_proxy github.com: libgit2/libgit2.git index test: cast times explicitly 2019-01-25T22:36:44+00:00 Edward Thomson ethomson@edwardthomson.com 2019-01-20T23:52:50+00:00 f25bb508cf7fd4da1427544fb48fba12c3c76e1c Cast actual filesystem data to the int32_t that index entries store. 
Cast actual filesystem data to the int32_t that index entries store.
index: use new enum and structure names 2018-12-01T10:46:44+00:00 Edward Thomson ethomson@edwardthomson.com 2018-11-28T13:31:06+00:00 18e71e6d597abe6c7feb666429c921bd19dc0ba8 Use the new-style index names throughout our own codebase. 
Use the new-style index names throughout our own codebase.
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 






index::racy: force racy entry
2016-03-08T05:47:55+00:00

Edward Thomson
ethomson@github.com

2016-03-07T22:37:17+00:00

53fb823bcc4d9206a768024026b7146cb4e1e507

Instead of hoping that we can get a racy entry by going real fast
and praying real hard, just create a racy entry.





Instead of hoping that we can get a racy entry by going real fast
and praying real hard, just create a racy entry.







tests: use legitimate object ids
2016-02-28T23:54:56+00:00

Edward Thomson
ethomson@github.com

2016-02-28T21:02:49+00:00

4afe536ba1c909ff8ab8d1b75997d3897b72571b

Use legitimate (existing) object IDs in tests so that we have the
ability to turn on strict object validation when running tests.





Use legitimate (existing) object IDs in tests so that we have the
ability to turn on strict object validation when running tests.







win32: introduce p_timeval that isn't stupid
2016-02-12T18:34:15+00:00

Edward Thomson
ethomson@github.com

2016-02-11T20:24:21+00:00

35439f5997c41d0c50d58997c2167ee93aad6c30

Windows defines `timeval` with `long`, which we cannot
sanely cope with.  Instead, use a custom timeval struct.





Windows defines `timeval` with `long`, which we cannot
sanely cope with.  Instead, use a custom timeval struct.







typos in comments
2015-12-21T19:18:07+00:00

Dmitriy Olshevskiy
olshevskiy87@bk.ru

2015-12-21T17:49:14+00:00

91f0d186b4efee8ccd5d0bbedf6b806a4f5e2a3a












tests: fix warning for nested struct initialization
2015-11-30T16:40:49+00:00

Patrick Steinhardt
ps@pks.im

2015-11-30T16:40:49+00:00

a7bd157ebfcfd517b65e0ddc017286f61bc8b218












Fix some warnings
2015-11-20T18:48:51+00:00

Jacques Germishuys
jacquesg@striata.com

2015-11-20T18:48:51+00:00

87428c556f36066040a79ffab416939a0ff9bae1












racy: make git_index_read_index handle raciness
2015-11-17T03:59:02+00:00

Edward Thomson
ethomson@microsoft.com

2015-11-16T23:06:52+00:00

5f32c50683cefaf51fa4f8825abfe533f36fe6f3

Ensure that `git_index_read_index` clears the uptodate bit on
files that it modifies.

Further, do not propagate the cache from an on-disk index into
another on-disk index.  Although this should not be done, as
`git_index_read_index` is used to bring an in-memory index into
another index (that may or may not be on-disk), ensure that we do
not accidentally bring in these bits when misused.





Ensure that `git_index_read_index` clears the uptodate bit on
files that it modifies.

Further, do not propagate the cache from an on-disk index into
another on-disk index.  Although this should not be done, as
`git_index_read_index` is used to bring an in-memory index into
another index (that may or may not be on-disk), ensure that we do
not accidentally bring in these bits when misused.