Skip to content

Docs: start basic template#1666

Merged
derrickstolee merged 2 commits intomicrosoft:masterfrom
derrickstolee:docs
May 27, 2020
Merged

Docs: start basic template#1666
derrickstolee merged 2 commits intomicrosoft:masterfrom
derrickstolee:docs

Conversation

@derrickstolee
Copy link
Contributor

@derrickstolee derrickstolee commented May 26, 2020

We don't have a lot of user-facing documentation. Someone owns VFSforGit.org but I don't know who. (@ethomson probably knows.)

However, it would be better to have a set of docs in the repo. This provides some basic info for using VFS for Git, especially around the happy path.

To finish #1665, I will update the troubleshooting docs with more advice around the not-so-happy paths.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
@dscho
Copy link
Member

dscho commented May 27, 2020

We don't have a lot of user-facing documentation. Someone owns VFSforGit.org but I don't know who. (@ethomson probably knows.)

I just had a look at https://www.whois.com/whois/vfsforgit.org. It seems that Microsoft holds it, but it will expire on July 12th this year... so we might need to get a couple cogs turning to renew it in time.

@derrickstolee
Copy link
Contributor Author

I just had a look at https://www.whois.com/whois/vfsforgit.org. It seems that Microsoft holds it, but it will expire on July 12th this year... so we might need to get a couple cogs turning to renew it in time.

Could we renew it to just redirect to this repo? I wonder if @mrfaizal has any idea what that process would look like.

Copy link
Member

@dscho dscho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No major issues found ;-)

* VFS for Git will work with any Git service that supports the
[GVFS protocol](Protocol.md). For example, you can create a repo in
[Azure DevOps](https://azure.microsoft.com/services/devops/), and push
some contents to it. There are two constraints:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really want to wrap the .md?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...yes? It links to the page in the repo. Perhaps I don't understand your comment.

some contents to it. There are two constraints:

* Your repo must not enable any clean/smudge filters
* Your repo must have a `.gitattributes` file in the root that includes
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it "that includes" or "whose contents consists of"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there are some .gitattributes options that can be added in addition to this one. I don't think an exact value is important.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
@derrickstolee derrickstolee merged commit 6c2a6d7 into microsoft:master May 27, 2020
derrickstolee added a commit that referenced this pull request Jun 2, 2020
Includes the following pull requests:

* #1663: Update Git to v2.27.0
* #1669: Docs: more troubleshooting and FAQs
* #1668: ProductUPgradeTimer: remove unacceptable Environment.Exit()
* #1664: Update USN journal entries for projected folders
* #1666: Docs: start basic template
* #1658: ProjFSFilter: Be more robust to missing PowerShell
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants