Jeff King 4bd481e0ad http: prefer CURLOPT_SEEKFUNCTION to CURLOPT_IOCTLFUNCTION
The IOCTLFUNCTION option has been deprecated, and generates a compiler
warning in recent versions of curl. We can switch to using SEEKFUNCTION
instead. It was added in 2008 via curl 7.18.0; our INSTALL file already
indicates we require at least curl 7.19.4.

But there's one catch: curl says we should use CURL_SEEKFUNC_{OK,FAIL},
and those didn't arrive until 7.19.5. One workaround would be to use a
bare 0/1 here (or define our own macros).  But let's just bump the
minimum required version to 7.19.5. That version is only a minor version
bump from our existing requirement, and is only a 2 month time bump for
versions that are almost 13 years old. So it's not likely that anybody
cares about the distinction.

Switching means we have to rewrite the ioctl functions into seek
functions. In some ways they are simpler (seeking is the only
operation), but in some ways more complex (the ioctl allowed only a full
rewind, but now we can seek to arbitrary offsets).

Curl will only ever use SEEK_SET (per their documentation), so I didn't
bother implementing anything else, since it would naturally be
completely untested. This seems unlikely to change, but I added an
assertion just in case.

Likewise, I doubt curl will ever try to seek outside of the buffer sizes
we've told it, but I erred on the defensive side here, rather than do an
out-of-bounds read.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2023-02-06 09:27:09 +01:00
2022-10-06 17:42:55 -04:00
2022-03-24 00:31:36 +01:00
2022-12-13 21:15:39 +09:00
2021-07-22 13:05:54 -07:00
2021-11-14 15:19:23 +01:00
2021-07-13 16:52:50 -07:00
2021-08-12 14:00:52 -07:00
2023-01-19 13:47:42 -08:00
2022-12-13 21:09:40 +09:00
2021-04-27 16:31:39 +09:00
2021-05-07 12:47:41 +09:00
2021-07-13 16:52:50 -07:00
2021-10-25 16:07:00 -07:00
2021-10-11 10:21:47 -07:00
2021-10-25 16:06:58 -07:00
2021-09-23 13:44:48 -07:00
2022-12-13 21:15:39 +09:00
2021-10-18 15:47:56 -07:00
2021-10-25 16:06:58 -07:00
2021-10-11 10:21:47 -07:00
2021-10-01 12:43:09 -07:00
2021-10-18 15:47:57 -07:00
2021-10-18 15:47:57 -07:00
2021-04-27 16:31:39 +09:00
2021-04-08 13:23:25 -07:00
2022-03-24 00:31:36 +01:00
2021-10-25 16:07:00 -07:00
2021-10-25 16:07:00 -07:00
2021-08-24 15:32:37 -07:00
2021-10-11 10:21:47 -07:00
2022-12-13 21:15:39 +09:00
2021-10-25 16:06:58 -07:00
2022-06-23 12:35:38 +02:00
2022-10-06 17:42:02 -04:00
2021-05-04 12:09:43 +09:00
2022-10-06 17:42:55 -04:00
2021-09-20 15:20:43 -07:00
2022-12-13 21:09:40 +09:00
2022-12-13 21:09:40 +09:00
2021-10-29 14:59:29 -07:00

Build status

Git - fast, scalable, distributed revision control system

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.

Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-<commandname>.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to git@vger.kernel.org (read Documentation/SubmittingPatches for instructions on patch submission). To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at https://lore.kernel.org/git/, http://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (depending on your mood):

  • random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
  • stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
  • "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
  • "goddamn idiotic truckload of sh*t": when it breaks
Description
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%