Re: [PATCH] mingw: use OpenSSL's SHA-1 routines
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- Feb 13, 2017, 21:07 UTC
- Message-ID
- <b530c820-9956-4396-d853-c7d70ccaf11d@kdbg.org>
- In-Reply-To
- <xmqq60kdev2r.fsf@gitster.mtv.corp.google.com>
Am 13.02.2017 um 20:42 schrieb Junio C Hamano:
Show 15 quoted lines
> I have been operating under the assumption that everybody on Windows > who builds Git works off of Dscho's Git for Windows tree, and > patches that are specific to Windows from Dscho's are sent to me via > the list only after they have been in Git for Windows and proven to > help Windows users in the wild. > > The consequence of these two assumptions is that I would feel safe > to treat Windows specific changes that do not touch generic part of > the codebase from Dscho just like updates from any other subsystem > maintainers (any git-svn thing from Eric, any gitk thing from Paul, > any p4 thing Luke and Lars are both happy with, etc.). > > You seem to be saying that the first of the two assumptions does not > hold. Should I change my expectations while queuing Windows specific > patches from Dscho?
Your first assumption is incorrect as far as I am concerned. I build from your tree plus some topics. During -rc period, I build off of master; after a release, I build off of next. I merge some of the topics that you carry in pu when I find them interesting or when I suspect them to regress on Windows. Then I carry around a few additional patches that the public has never seen, and these days I also merge Dscho's rebase-i topic.
-- Hannes