git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: git <git@vger.kernel.org>, 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 18:15:01 +0200	[thread overview]
Message-ID: <CAP8UFD0gO0Qaip84Q+dOzCwirTOEQnJNCeBQrBmCzvjQ6s2KCA@mail.gmail.com> (raw)
In-Reply-To: <8fb4c61f-56fb-6650-d12e-7aea5f48828a@iee.email>

Hi Philip,

On Thu, Apr 23, 2020 at 1:44 PM Philip Oakley <philipoakley@iee.email> wrote:

> 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

This one had already been added by Jakub in:

https://github.com/git/git.github.io/commit/44e19bb6ce35fccb67d0e45087602a8b586bde01

> 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.

Thanks! I just added this one at the end of the "Light reading" in the edition:

https://github.com/git/git.github.io/blob/master/_posts/2020-04-23-edition-62.markdown

> Both of which were interesting and potentially useful.

Sure!

Best,
Christian.

      reply	other threads:[~2020-04-23 16:15 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
2020-04-23 16:15   ` Christian Couder [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=CAP8UFD0gO0Qaip84Q+dOzCwirTOEQnJNCeBQrBmCzvjQ6s2KCA@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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 \
    --cc=philipoakley@iee.email \
    /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).