From: "Philip Oakley" <philipoakley@iee.org>
To: "Git List" <git@vger.kernel.org>,
"git-for-windows" <git-for-windows@googlegroups.com>,
"Git Users" <git-users@googlegroups.com>
Cc: "Stefan Beller" <sbeller@google.com>
Subject: Git Merge 2017 Videos
Date: Sun, 4 Jun 2017 11:24:17 +0100 [thread overview]
Message-ID: <9AC6BDC64AEE4E76B505094B1BADE2D7@PhilipOakley> (raw)
While looking at the recent .gitignore issue (the need to use `**`) I came
up against a comment in
https://public-inbox.org/git/CAGZ79kZQsauBfoTjyqm+-+LjyyEc2Ykj5exUY5KdErEzFH0GMA@mail.gmail.com/
noting that the Git Merge 2017 videos were not available at that time.
Well, a search found them on Youtube on the GitHub channel :
https://www.youtube.com/results?search_query=git+merge+2017+videos
With a playlist :
https://www.youtube.com/watch?v=tvymSWfvkjw&list=PL0lo9MOBetEGRAJzoTCdco_fOKDfhqaOY
Enjoy the viewing. The first few have been good.
--
Philip
next reply other threads:[~2017-06-04 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 10:24 Philip Oakley [this message]
2017-06-04 17:36 ` Git Merge 2017 Videos Kevin Daudt
2017-06-04 18:45 ` Christian Couder
2017-06-04 22:03 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9AC6BDC64AEE4E76B505094B1BADE2D7@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git-for-windows@googlegroups.com \
--cc=git-users@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox