On Saturday 20 January 2007 04:31, Shawn O. Pearce wrote:
> Base your branch on Junio's 'master', not 'next'. This looks like
> its going to be a fairly long-running topic with a large number
> of commits. It will be easier to convince Junio to pull the topic
> in if its based solely on 'master' than if its based on 'next'.
I consider this branch only the sandbox for the MinGW port.
Although I've tried to make the branch as clean as possible, it is still a bit
messy, and not everything is #ifdef'd that should be. For this reason I will
not try to convince Junio to pull this topic directly. The goal is rather to
work towards a complete port, then later factor out patches that
bring 'master' or 'next' closer to this branch so that finally only at most a
small patch series is needed that contains this topic.
> git-compat-util:
> #ifdef __MINGW32__
> #define is_mingw32 1
> #else
> #define is_mingw32 0
> #endif
>
> everywhere else:
> if (is_mingw32) {
> }
I like this idea.
-- Hannes
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html