From: Philip Oakley <philipoakley@iee.email>
To: Christian Couder <christian.couder@gmail.com>, git <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Jakub Narebski <jnareb@gmail.com>,
Markus Jansen <mja@jansen-preisler.de>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Draft of Git Rev News edition 62
Date: Thu, 23 Apr 2020 12:44:49 +0100 [thread overview]
Message-ID: <8fb4c61f-56fb-6650-d12e-7aea5f48828a@iee.email> (raw)
In-Reply-To: <CAP8UFD2iR2TOoU-HJvOiQvZhJ+ebxX6zs+KfM-CCFKHSYuwNSg@mail.gmail.com>
Hi Christian,
(cc list trimmed because of local sender limits)
On 21/04/2020 11:50, Christian Couder wrote:
> Hi everyone!
>
> A draft of a new Git Rev News edition is available here:
>
> https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-62.md
>
> Everyone is welcome to contribute in any section either by editing the
> above page on GitHub and sending a pull request, or by commenting on
> this GitHub issue:
>
> https://github.com/git/git.github.io/issues/427
>
> You can also reply to this email.
>
> In general all kinds of contribution, for example proofreading,
> suggestions for articles or links, help on the issues in GitHub, and
> so on, are very much appreciated.
>
> I tried to cc everyone who appears in this edition, but maybe I missed
> some people, sorry about that.
>
> Jakub, Markus, Kaartic and me plan to publish this edition on Thursday
> April 23rd in the evening.
>
> Thanks,
> Christian.
A couple of light reading articles were mentioned in the stackoverflow
blog #17
https://stackoverflow.blog/2020/04/17/the-overflow-17-legally-beige/
(verbatim extracts)
1. CS visualized: Useful Git commands
<https://dev.to/lydiahallie/cs-visualized-useful-git-commands-37p1>
https://dev.to/lydiahallie/cs-visualized-useful-git-commands-37p1
Oftentimes though we use commands that we know work, but we don’t
understand how they work under the hood! Here is a great series of
visualizations of git commands to understand them more at a theoretical
level
2. The phases of remote adaptation
<https://about.gitlab.com/company/culture/all-remote/phases-of-remote-adaptation/>
https://about.gitlab.com/company/culture/all-remote/phases-of-remote-adaptation/
GitLab put together a really interesting list of phases for teams
switching from a colocated environment to a remote one. It’s a good
reflection on how your team culture might work, and how to be prepared
for changes.
Both of which were interesting and potentially useful.
--
Philip
next prev parent reply other threads:[~2020-04-23 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 10:50 Draft of Git Rev News edition 62 Christian Couder
2020-04-23 11:44 ` Philip Oakley [this message]
2020-04-23 16:15 ` Christian Couder
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=8fb4c61f-56fb-6650-d12e-7aea5f48828a@iee.email \
--to=philipoakley@iee.email \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=mja@jansen-preisler.de \
--cc=peff@peff.net \
/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;
as well as URLs for NNTP newsgroup(s).