Git User's Survey 2010 is now up!

[TheLemming]

[copied from an email sent to projects which use Git. The 'we' here refers to the Git developers].

We would like to ask you a few questions about your use of the Git

version control system. This survey is mainly to understand who is

using Git, how and why.

The results will be published to the Git wiki on the GitSurvey2010

page (https://git.wiki.kernel.org/index.php/GitSurvey2010) and

discussed on the git mailing list ([email protected]).

The survey would be open from 1 September till 15 October 2010.

Please devote a few minutes of your time to fill this simple

questionnaire, it will help a lot the git community to understand your

needs, what you like of Git, and of course what you don't like of it.

The survey can be found here:

http://tinyurl.com/GitSurvey2010

https://www.survs.com/survey/MUPYR8UJ4B

Git User's Survey 2010 was originally announced on git mailing list

in the following mail:

http://article.gmane.org/gmane.comp.version-control.git/154986

[TheLuda]

Already done. Git really needs directory tracking. I still don't get it, why this is a no go in 2010

[DasBlub]

Already done. Git really needs directory tracking. I still don't get it, why this is a no go in 2010

some systems like z/OS simply don't have folders

just create .CREATEDIR (or similar name) in the directory and add it to the repo -> you have your folder

[freghar]

Well git _does_ support directories, it just don't add new empty directories to the repository. You can - in theory - have an empty tree object representing some directory, but storing such object might seem meaningless to some people.

[TheLuda]

Well, and not supporting directories properly with permissions stored actually is an issue in some cases.

E.g. most forum apps have a cache directory which is empty by default, and writable for the host. With git, and any other version control system, I add the empty directory with a dummy file like .gitignore and git will not store the directory permissions in that case like it does for file permissions.

Each branch switch, the directory is switch to default permissions, and not writable anymore. Yes, I could tell users to create and setup the folder every time. But hey... many forget and who gets the support call? I know, its' probably silly.

[Schmoozerd]

add a post-checkout hook?