Question: IE6/7 don't support "box-sizing: border-box" but they render all boxes as a "border-box" on quirks mode.
And I need a css grid(like in bootstrap.css) based on the border-box model which can run in 6/7. 

Could any one tell a way to switch to quirks mode ONLY on IE6/7 (doesn't affect IE8 or higher)? Thanks!

Answer: 
There is no way to sync 2 repositories evolving separatly 100% automaticaly with whatever solution you choose (to achieve automatic sync, you must either achieve a sync in no time or being able to block push in git or check in in TFVC when one of the 2 team begin a sync) .

So, you will always have conflicts that you should merge manualy. You could find a workflow that will prevent most of them but never solve all the cases and these remaining cases will be really difficult to solve...

Anyway, you could nearly achived what you want (it depends of your expectations : do you need branching support --hard--,...) with git-tfs (I have included in git-tfs all needed to do that but never used in production) but it's a little bit tricky.

You need to clone your TFS repository in a `bare` repository :

`git tfs clone https://server/tfs/TeamCollection $/project/trunk --bare --with-branches`

then you need to write in your `post-receive` hook of this `bare` repository something like that (I do not remember if it works) :

```
branch=$(git rev-parse --symbolic --abbrev-ref $1)
if [ "master" == "$branch" ]; then
    branch="default" 
fi
git tfs rcheckin --bare -i $branch

```

With that, every time someone push in the git repository, the commits will be checked in in TFS.

For more comfort (otherwise they will always have boring conflicts to solve when they try to push), you could sync git repository with TFS server with a scheduled task with the command (this way they will be aware of new commits sooner) :

```
git tfs fetch --all

```

Note : I don't remember if this command could be used in a `bare` repository (now that I think about that, I don't think so). Otherwise you will have to use instead `git tfs fetch -b=myGitBranch -i tfsRemote` for each existing branch :( 

But I'm sure they will never be able to work with branches that was not already created in tfs :( The git-tfs tool is indeed not able to create automatically a TFVC branch from a git history. Technically, that's achievable, I think, but never developed (because git-tfs is more à tool to run away of TFVC than a tool to check your development in it... ) 

And some other stuff could be difficult or impossible to do...

I hope it will help.

PS :

* that's a hard job you are trying to do for someone not used to git-tfs...and something I don't recommend to do.
* I highly recommend to go the same way Microsoft is taking and to migrate everything on git (even staying on TFS server or VSTS if needed), that way the sync will be a lot easier (even if not 100% automatic ;-)). I have made a good doc on how to migrate from TFVC: <https://github.com/git-tfs/git-tfs/blob/master/doc/usecases/migrate_tfs_to_git.md>
* Try to convince your enterprise that each team should choose and master its tools and not be imposed some choices.
The main change since that question was asked (in Q4 2013) is that TFS 2015/2017 now has an official support for Git repositories. See "[Git and TFS](https://learn.microsoft.com/en-us/vsts/git/overview)".

So a reasonable approach would be to:

* use a tool like [git-tfs](https://github.com/git-tfs/git-tfs) to export the existing TFS project history into a new Git repository.
* split-up that Git repo into one main codebase, and several smaller repos, each one representing the part you want other contributors to access to
* reference those [sub-repos as **submodules**](https://git-scm.com/book/en/v2/Git-Tools-Submodules) in the main codebase
* finally, create TFS projects (this time using Git repos) in order to push back those repos to the TFS server.

That will leave you with a collection of TFS projects, each one can be opened to a particular team, ensuring that only specific parts are visible/accessible to other contributors.

And at any time; from the main coderepo repo, you can [update those submodules with](https://stackoverflow.com/a/1979194/6309): 

```
git submodule update --recursive --remote --rebase

```

(and then test, add, commit and push: your main Git repo will reference the latest developments from those submodules)

Plus, considering [`l--''''''---------''''''''''''`](https://stackoverflow.com/users/117700)'s [previous question](https://stackoverflow.com/a/47446422/6309), that would help with a single repo with too many files.  

Although, for that, [there will be soon(ish) GVFS](https://blogs.msdn.microsoft.com/devops/2017/02/03/announcing-gvfs-git-virtual-file-system/).

---

The alternative approach mentioned by [`l--''''''---------''''''''''''`](https://stackoverflow.com/users/117700) is:

> 
> I personally want to be able to use GIT for my own changes, I would
>  have multiple changesets in GIT, then I would merge them into one, and
>  then convert that changeset into a traditional TFS changeset and check
>  that in, that way I just have 1 check-in per TFS item
> 
> 
> 

That is possible, provided you don't mind losing the intermediate Git commit history, when you will agregate them into one TFS changeset.