[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: The state and future of the git/mingw** reposiories?
From:       Johannes Sixt <johannes.sixt () telecom ! at>
Date:       2008-08-20 20:18:35
Message-ID: 200808202218.35626.johannes.sixt () telecom ! at
[Download RAW message or body]

On Mittwoch, 20. August 2008, Petr Baudis wrote:
>   Hi,
>
>   I'm currently doing some MSysGit hacking (mostly git-gui-related) and
> I'm wondering what should I actually base my work on, considering the
> statement of 1.6.0 release notes:
>
> 	Source changes needed for porting to MinGW environment are now
> 	all in the main git.git codebase.

If all you need is a mostly working git, you can build off of git.git 
(assuming you have the build environment that msysgit provides).

> However, git diff junio/master...mingw/master shows quite a few
> differences - is there any plan to merge these?

You see three kinds of differences:

- Changes in the test suite.
- Perl related changes (most notably, git-add--interactive in git.git does not 
work on MinGW without these changes).
- One or two gitk related fixes.

All of them will be sent upstream some day.

If you need one of the areas that these changes touches, then you can work off 
of mingw.git.

> If so, do you plan to 
> maintain the mingw fork indefinitely anyway as a staging area for your
> patches that you plan to push upstream, or is it going to be phased out
> eventually?

I hope I can reset mingw.git to git.git some day. But I plan to keep it as 
staging area for patches.

-- Hannes
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]