git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[fyi] patches used by git distributors

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Nov 8, 2011, 09:02 UTC
Message-ID
<20111108090251.GB17954@elie.hsd1.il.comcast.net>
Hi,

In an ideal world, each patch applied by downstream distributors would fall into one of two categories: (a) adapting the package to some esoteric distro-specific requirement (i.e., special-interest patches) or (b) in the process of being generalized and reviewed for eventual application upstream, so everyone can benefit from it. Unfortunately that takes time. I should do better --- sorry about that.

As an experiment, here's a quick summary of the patches being used in Debian, for people curious about that and for people interested in grabbing useful patches to polish and not knowing where to start.

(Links point to relevant discussion, not necessarily the patch used):
Frédéric Brière (1):
      gitk: Skip over AUTHOR/COMMIT_DATE when searching all fields [1]
Gerrit Pape (1):
      bug#506445: hooks/post-receive-email: set encoding to utf-8 [2]
Jonathan Nieder (12):
      remove shebang line from shell libraries [3]
      pre-rebase hook: capture documentation in a <<here document [4]
      gitk: use symbolic font names "sans" and "monospace"
      transport: expose git_tcp_connect and friends in new tcp.h [5]
      daemon: make host resolution into a separate function [5]
      daemon: move locate_host to tcp.c [5]
      tcp: unify ipv4 and ipv6 code paths [5]
      daemon: check for errors retrieving IP address [5]
      tcp: make dns_resolve return an error code [5]
      transport: optionally honor DNS SRV records [5]
      srv: make errors less quiet [5]
      Makefile: add a knob to turn off hardlinks within same directory [6]

The patches listed above are on the candidate+patches branch of [7]. Questions and improvements can go to git@packages.debian.org.

A few other packaging projects:
 - git://pkgs.fedoraproject.org/git.git master --- 3 patches (using
   SERVER_NAME for home link, reviving vc-git.el, compatibility with
   newer cvsps)
 - http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/git/files/ ---
   1 patch (capping individual reads and writes at INT_MAX chars)
 - https://build.opensuse.org/package/files?package=git&project=devel%3Atools%3Ascm
   --- 4 patches (a python build fix, making gitweb::prevent_xss
   default to true, turning off hardlinks for builtins at installation
   time, protecting COMP_WORDBREAKS from mangling in the completion
   script)
 - http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-vcs/git/files/
   --- 1 patch (a NO_CVS knob for the makefile).  Very nice.
 - http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/devel/scmgit-base/patches/
   --- 3 patches (putting CFLAGS at the end of ALL_CFLAGS so it can
   override BASIC_CFLAGS, setting INSTALLDIRS=vendor in perl makefile,
   improving tk support on Darwin 8)
 - http://www.openbsd.org/cgi-bin/cvsweb/ports/devel/git/patches/ ---
   8 patches (updating OpenBSD makefile defaults, using raw perlio in
   gitweb blob view, removing "set -e" in t9117, passing --text [well,
   -a] to grep in t9200, avoiding nonportable regex \+ in t9400)
 - ftp://ftp.cygwin.org/pub/cygwin/release/git/git-1.7.5.1-1-src.tar.bz2
   --- 3 patches (tcl 8.4.1 support, updating Cygwin makefile defaults,
   case-insensitive path comparison in makefile, special Windows-specific
   wish script preamble)
[1] http://thread.gmane.org/gmane.comp.version-control.git/142160
[2] http://thread.gmane.org/gmane.comp.version-control.git/181737
[3] http://bugs.debian.org/368792
[4] http://thread.gmane.org/gmane.comp.version-control.git/150737
[5] http://thread.gmane.org/gmane.comp.version-control.git/175106
[6] http://thread.gmane.org/gmane.comp.version-control.git/183361
[7] http://smarden.org/git/git.git
    gitweb: http://repo.or.cz/w/git/debian.org
Next: Junio C Hamano
Message 1 of 6 in “[fyi] patches used by git distributors”
  1. Jonathan NiederNov 8, 2011
  2. Junio C HamanoNov 8, 2011
  3. Junio C HamanoNov 8, 2011
  4. pre-rebase hook: capture documentation in a <<here documentJonathan Nieder, Mar 8, 2012
  5. Erik Faye-LundNov 10, 2011
  6. Todd ZullingerNov 10, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.