Comments on: Git and our friction points and beginners mistakes

By: Mike

Mike — Wed, 11 Aug 2010 16:02:07 +0000

OK. I was surprised when I cloned the G: drive back to the C: all the source files were there.

Great article.

By: Gabriel N. Schenker

Gabriel N. Schenker — Wed, 11 Aug 2010 13:53:32 +0000

No, on the backup there is only the repository (the .git folder)

By: Mike

Mike — Wed, 11 Aug 2010 11:21:14 +0000

On the backup to your g: drive, do you include the source files as well? I tired the above and had to use –no-hardlinks option to push the source files to my own g: drive.

By: Paul Batum

Paul Batum — Sat, 19 Jun 2010 02:21:33 +0000

I can confirm that git extensions will give you easy access to blame from within visual studio. Its pretty much the only reason I have git extensions installed.

By: Ike

Ike — Fri, 18 Jun 2010 18:52:37 +0000

git commands from within vs.
I haven’t tested this myself (I’m not using git).

http://gitscc.codeplex.com/

By: Gabriel N. Schenker

Gabriel N. Schenker — Fri, 18 Jun 2010 15:42:23 +0000

@bogardj: Jimmy, thanks for your suggestion. But in the mean time we came up with another solution that will work for us. I’ll probably have another blog post about this

By: bogardj

bogardj — Fri, 18 Jun 2010 15:29:58 +0000

Rails migrations use a timestamp like:

20100618102835

yyyyMMddhhmmSS

We automated the generation of our change scripts through NAnt and RedGate SQL Compare (which has a command line tool). If you don’t have that, you can create a simple script that generates an empty SQL file with a name and the current date, like:

genSql.bat My_Desc_of_change

By: Peter Lehmann

Peter Lehmann — Fri, 18 Jun 2010 14:43:02 +0000

well i am not 100% sure but i think Git extensions can give blame i visual studio, check the project out at http://code.google.com/p/gitextensions/

i only use it for log as it is a lot better then gitk