On Thursday 24 January 2008 18:07:57 Reece Dunn wrote:
> If you are in a bash/cmd shell *on Windows* with a checked out
> wine.git repository, and you are using VCExpress to *build and test*
> the /tests/ that test the Windows platforms (that is, you either don't
> have access to mingw, or want to
On 24/01/2008, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> "Reece Dunn" <[EMAIL PROTECTED]> writes:
>
> > and when everything is ok:
> >
> > git add . && git status
> > git commit -m "user32: fixed edit for ."
> >
> > which won't work in this case, as the files that cl generates will be
On Thu, 24 Jan 2008, Reece Dunn wrote:
[...]
> and when everything is ok:
>
> git add . && git status
> git commit -m "user32: fixed edit for ."
>
> which won't work in this case, as the files that cl generates will be
> added into the local repository.
Then just specify which files to c
"Reece Dunn" <[EMAIL PROTECTED]> writes:
> and when everything is ok:
>
> git add . && git status
> git commit -m "user32: fixed edit for ."
>
> which won't work in this case, as the files that cl generates will be
> added into the local repository.
You should add them to your global .git
On 24/01/2008, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
> "Reece Dunn" <[EMAIL PROTECTED]> wrote:
>
> > This patch ignores any files generated by the Visual C++ compiler to
> > make it easier to generate patches when using the VCExpress family of
> > compilers on Windows.
>
> There is no point i
> "Dmitry" == Dmitry Timoshkov <[EMAIL PROTECTED]> writes:
Dmitry> "Reece Dunn" <[EMAIL PROTECTED]> wrote:
>> This patch ignores any files generated by the Visual C++ compiler to
>> make it easier to generate patches when using the VCExpress family of
>> compilers on Windows.
"Reece Dunn" <[EMAIL PROTECTED]> wrote:
> This patch ignores any files generated by the Visual C++ compiler to
> make it easier to generate patches when using the VCExpress family of
> compilers on Windows.
There is no point in that, patches should be generated after testing
in Wine under a suppo
