Meta tags:
description=We bring the awesome Git VCS to Windows;

Headings (most frequently used words):

windows, git, for, case, paths, preservation, insensitivity, path, quotation, executable, and, mode, bits, core, filemode, drive, vs, bash, rooted,

Text of the page (most frequently used words):
the (31), git (18), #windows (14), and (13), case (12), this (10), executable (10), file (10), for (9), that (6), bit (6), will (6), linux (6), repository (5), path (5), not (5), branch (5), paths (4), config (4), mode (4), bits (4), map (3), bash (3), out (3), files (3), core (3), filemode (3), may (3), other (3), are (3), which (3), can (3), filenames (3), vim (3), names (3), site (2), discussions (2), faq (2), home (2), drive (2), conversion (2), need (2), some (2), when (2), with (2), see (2), set (2), necessary (2), tree (2), locally (2), system (2), semantics (2), sensitive (2), preserving (2), wrong (2), setting (2), cause (2), users (2), where (2), use (2), chmod (2), especially (2), one (2), quoting (2), between (2), common (2), but (2), has (2), addition (2), any (2), special (2), characters (2), means (2), quotation (2), lower (2), version (2), main (2), usage (2), classic, letter, replaced, implicit, directory, commonly, used, absolute, rooted, filesystems, lose, marked, checked, checks, non, clone, init, probe, filesystem, handles, correctly, variable, automatically, tells, working, honored, from, https, scm, com, docs, corefilemode, configuration, records, cloned, local, change, unless, actually, trust, mis, unexpected, effects, damage, don, internet, ever, probably, directly, manipulate, shows, how, option, while, adding, updating, stackoverflow, page, attaches, word, each, indicate, readable, writable, ownership, aspects, does, well, existing, retained, meta, data, then, held, index, many, commands, report, errors, way, maybe, expected, simply, ignore, invalid, options, leaving, unfamiliar, user, wondering, what, happened, area, happen, there, confusion, single, double, none, cmd, powershell, thread, spaces, rare, like, multiple, mechanisms, accept, character, filename, including, imperfect, dependant, particular, command, structure, terminal, also, cannot, checkout, contain, such, colon, etc, cross, management, issues, likewise, able, check, both, upper, apparently, two, versions, problem, different, even, though, often, mistake, because, read, normal, have, difficulty, meets, changed, stored, insensitive, meanwhile, posix, designed, preservation, insensitivity, modes,

Text of the page (random words):
file names branch names path quotation executable bit and file modes core filemode home faq repository discussions site map git for windows case preservation case insensitivity windows is case insensitive but case preserving for filenames meanwhile linux posix for which git is designed is case sensitive in addition git branch names are stored as filenames this means that in normal usage git will have difficulty when it meets a changed case file or branch lower case is common for linux usage e g main branch and main branch are different even though on windows git will often mistake one for the other because windows will read the other case version of the file likewise windows will not be able to check out both an upper case and lower case version of a file s apparently the vim repository has this two versions vim vim problem windows also cannot checkout files which contain special characters such as colon etc this can cause cross system management issues path quotation spaces in filenames is common in windows but rare in linux linux has like windows multiple path quoting mechanisms in addition linux can accept any character in any filename including special characters this means that the path conversion between windows and git is imperfect and dependant on the particular command structure and terminal in use many git commands do not report errors in the way that maybe expected by windows users some will simply ignore invalid options and paths leaving the unfamiliar user wondering what happened the git config is one area where this may happen especially as there can be quoting confusion single double or none between bash cmd and powershell e g see thread executable and mode bits linux attaches a mode word to each file with bits that indicate if the file is executable readable writable and other ownership aspects chmod this does not map well to windows semantics especially for the executable bit the existing mode bits are retained in the repository tree meta data which is then held locally in the index users may need to directly manipulate the mode bits where necessary the stackoverflow page shows how to use the chmod option while adding or updating files core filemode the core filemode configuration records for the locally cloned repository the local file system semantics i e is it case sensitive case preserving or not do not change this unless it is actually set wrong git will trust this setting and mis setting it may cause unexpected effects and damage don t do it the internet as ever is probably wrong from https git scm com docs git config git config corefilemode tells git if the executable bit of files in the working tree is to be honored some filesystems lose the executable bit when a file that is marked as executable is checked out or checks out a non executable file with executable bit on git clone 1 or git init 1 probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary windows drive c paths vs bash rooted paths in the git for windows bash the classic c drive letter is replaced by the the implicit c directory path this conversion is commonly used in the git config paths that need to be absolute home faq repository discussions site map git for windows