On Nov 07, 2012, at 02:15 PM, David Nadlinger <code@klickverbot.at> wrote:

>  Directly accessing the tool binaries (the ones with a hyphen) is not officially supported on Linux either. For example, on Arch Linux they are installed into /usr/lib/git-core, which is not on the $PATH.

I have never used the tools binaries directly.

--
/Jacob Carlborg

On 7 November 2012 14:13, David Nadlinger <code@klickverbot.at> wrote:
> On Tue, Nov 6, 2012 at 9:24 PM, Walter Bright <walter@digitalmars.com> wrote:
>> Yeah, I know it's not the
>> usual git workflow, but git sux on Windows, and I don't care for the grief.
>
> Sorry, but I think you are just unnecessarily making life hard for yourself. What exactly is so bad about Git on Windows that it justifies manually copying the files over to a Linux box, with all the additional problems/chaos this entails? We might be able to help. Also note that the quality of Git on Windows has been improving a lot lately (at least in my experience), so if you have tried it the last time a few years ago, you might want to give it another shot.

At least for the git release I've used, which is about a year old. I
would describe its level of maturity as fairly similar to DMD - as
good as DMD, and as bad as DMD.
I was never able to get git to work from the Windows command prompt.
Other people have apparently done that, but I never had any success
with it. But from the git bash shell, it works fine.
So, on Windows I always have a git shell open just for doing commits.

The key thing I found you must NOT do is have cygwin and Msys git both installed. As far as I can tell, git does no revision checking on its index files, so if you accidentally mix git versions, you'll corrupt various files, and get really bizarre symptoms. Some other oddities I've seen may be because I'm on German Windows -- some apps report error messages in English, others in German, and I think some scripts fail when they're expecting a particular language.

Walter -
I never had any problems with Windows git, IF AND ONLY IF I used it
from the git bash shell. It does seem broken elsewhere.
I recommend you use the pull tester, I think it will save you a lot of work.

-Don,



>
> If you don't want to use GitHub for testing your commits before pushing them to master, I'd suggest not copying over the files from your development box to the other ones where you run the test suite, but instead exporting the respective Git repositories as a network share and pulling the new commits from them using Git.
>
> This way, you could easily catch missing files and other problems like that. Let me emphasize that broken commits are indeed very annoying when you are trying to make sense of the history, for example when using »git bisect« (yes, there is »git bisect skip«, but it's still cumbersome).
>
> David
> _______________________________________________
> dmd-internals mailing list
> dmd-internals@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-internals
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

Jonathan M Davis, el  7 de November a las 04:07 me escribiste:
> On Wednesday, November 07, 2012 12:38:49 Leandro Lucarella wrote:
> > Walter Bright, el  6 de November a las 22:12 me escribiste:
> > > On 11/6/2012 9:04 PM, Brad Roberts wrote:
> > > >On 11/6/2012 7:44 PM, Walter Bright wrote:
> > > >>I do run the test suite locally before committing.
> > > >
> > > >On all platforms?  On the code you _actually_ committed not vs what you have in some other client?
> > > >
> > > >Based on the frequency of omitting a file and/or seeing a broken build, the answer to both of those is all too often 'no'.  Both of which would be true if you followed the pull + merge model that everyone else follows.>
> > > I run it on all the platforms but FreeBSD64 and then copy the files to the git repository on Linux.
> > 
> > That clearly doesn't detect errors when you forgot to commit stuff. Is NOT the same as going through the autotester which compiles everything from a fresh checkout.
> 
> Well, there are really 2 problems here.
> 
> 1. Copying files across rather than using git on Windows.
> 
> 2. Committing directly instead of creating pull requests and letting the pull tester test them.

Yes, but 1. is about Walter's personal life and 2. is a D problem. If Walter think is better for him to copy files around, fine with me, as long as he doesn't break the repository. That's why I'm concentrating in 2. Follow the rules as everybody else to minimize the occurrence of these kind of errors.

-- 
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals