Skip to content

Conversation

HonkingGoose
Copy link
Contributor

@ben My observations while fixing chapter 9:


client-bzr.asc:
Bazaar still uses http:// for their website...


client-hg.asc:
Mercurial still links to the http selenic repo when cloning, this is even mentioned in their own wiki, so this can stay.


client-p4.asc:
I don't know anything about perforce, so I'm not touching things here.
https://www.perforce.com/products doesn't list Git Fusion anymore, is this still relevant? Git Fusion is not EOL, as can be seen here: https://www.perforce.com/maintenance-support#eol_schedule


client-svn.asc:
I don't know anything about Subversion, so I'm not touching things here.


client-tfs.asc:
Changed Visual Studio link.


import-svn.asc:
I don't know anything about Subversion, so I'm not touching things here.


@ben
Copy link
Member

ben commented Mar 20, 2019

perforce.com/products doesn't list Git Fusion anymore, is this still relevant?

IIRC it's not a product, it's a feature of the core Perforce product. https://www.perforce.com/manuals/git-fusion/

@ben ben merged commit 5156e7a into progit:master Mar 20, 2019
@HonkingGoose
Copy link
Contributor Author

Ah okay, I don't use Perforce, so I was not aware that Git Fusion was included in the core Perforce product. 😄

@HonkingGoose HonkingGoose deleted the chapter_9_https branch March 20, 2019 16:28
@ben
Copy link
Member

ben commented Mar 20, 2019

Neither do I. 😄 I had to learn a lot to write this chapter.

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.

2 participants