From: "Philip Oakley" <philipoakley@iee.org>
To: "Christian Couder" <christian.couder@gmail.com>,
"Kevin Daudt" <me@ikke.info>
Cc: "Git List" <git@vger.kernel.org>,
"git-for-windows" <git-for-windows@googlegroups.com>,
"Git Users" <git-users@googlegroups.com>,
"Stefan Beller" <sbeller@google.com>
Subject: Re: Git Merge 2017 Videos
Date: Sun, 4 Jun 2017 23:03:33 +0100 [thread overview]
Message-ID: <982615C29E2046649A631B68E3F30235@PhilipOakley> (raw)
In-Reply-To: CAP8UFD08ckHsduwVBaGRr9WPALXjzOd-kc3zHZrHxo-HgGZ4hA@mail.gmail.com
From: "Christian Couder" <christian.couder@gmail.com>
> On Sun, Jun 4, 2017 at 7:36 PM, Kevin Daudt <me@ikke.info> wrote:
>> On Sun, Jun 04, 2017 at 11:24:17AM +0100, Philip Oakley wrote:
>>> 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.
>>
>> Thanks for sharing this.
>
> This was in the last edition of Git Rev News:
> https://git.github.io/rev_news/2017/05/17/edition-27/
>
I'd completely missed that. It was in the Other News, various, section.
(as an aside, your email is the first I've noticed that I think got
swallowed by my ISP's spam filter, though Eric's PublicInbox came to the
rescue with it's mbox export!)
prev parent reply other threads:[~2017-06-04 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 10:24 Git Merge 2017 Videos Philip Oakley
2017-06-04 17:36 ` Kevin Daudt
2017-06-04 18:45 ` Christian Couder
2017-06-04 22:03 ` Philip Oakley [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=982615C29E2046649A631B68E3F30235@PhilipOakley \
--to=philipoakley@iee.org \
--cc=christian.couder@gmail.com \
--cc=git-for-windows@googlegroups.com \
--cc=git-users@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=me@ikke.info \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).