On Jun 30, 2008, at 8:47 PM, Johannes Sixt wrote:
Then there are the extra patches in 4msysgit. From my POV, they are
not
_required_ because I can appearently work with git on Windows
without them. I
think some of them are not necessary. Can we go through them again?
I'll send a patch series in reply to this mail that contains the
following patches:
[PATCH 01/12] Fake reencoding success under NO_ICONV instead of
returning NULL.
[PATCH 02/12] Do not complain about "no common commits" in an empty
repo
[PATCH 03/12] MinGW: Convert CR/LF to LF in tag signatures
[PATCH 04/12] Avoid calling signal(SIGPIPE, ..) for MinGW builds.
[PATCH 05/12] Windows(msysgit): Per default, display help as HTML in
default browser
[PATCH 06/12] connect: Fix custom ports with plink (Putty's ssh)
[PATCH 07/12] Fixed text file auto-detection: treat EOF character
032 at the end of file as printable
[PATCH 08/12] fast-import: MinGW does not have getppid(). So do not
print it.
[PATCH 09/12] We need to check for msys as well as Windows in add--
interactive.
[PATCH 10/12] Add ANSI control code emulation for the Windows console
[PATCH 11/12] verify_path(): do not allow absolute paths
[PATCH 12/12] [TODO] setup: bring changes from 4msysgit/next to next
This series would bring *.{c,h,sh,perl} on Junio's next to 4msysgit/
next,
except for some minor differences (whitespace, comments, a workaround in
git-parse-remote.sh).
Steffen
