Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add shout-out during GitMerge 2017 #126

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wilsonmar
Copy link

No description provided.

@mhagger
Copy link
Owner

mhagger commented May 30, 2017

Thanks for the suggestion.

The main point of the README is to explain git-imerge and teach people how to use it. I don't think the main body of the README is a good place for "look, somebody mentioned git-imerge" links. Since this shout-out is not very pedagogical, I don't think it belongs here in the text. I wouldn't want people who are trying to learn about how to use git-imerge to click on it, because it wouldn't have value to them.

Arguably the GitMinutes link falls in the same category. I haven't listened to it for a while, but I don't recall it being a very good resource for learning how to use git-imerge.

By contrast, @patrickmckenna's talk from Git Merge 2016 would be a good pedagogical link. But I can't find it online so maybe it wasn't recorded.

Instead, maybe it would make sense to add a new "Other git-imerge links" section where we could collect significant mentions of git-imerge from around the web.

By the way, I think the way you have defined the link doesn't actually expose it to the reader unless there is a reference to it from the text.

@patrickmckenna
Copy link

I don't believe we recorded any of the training sessions from Git Merge 2016, unfortunately. However, my talk was essentially an extended version of the one Michael gave in 2013, which is currently linked to in the README. (I did post my slides, but the rendered versions require a remark-based tool that GitHub discontinued building and thus never open-sourced—so I doubt they'd be very useful.)

@abitrolly
Copy link
Contributor

So how about a separate entry with links mentioning git-imerge?

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.

4 participants