From: Taylor Blau <email@example.com>
To: Derrick Stolee <firstname.lastname@example.org>
Cc: Andrew Ardill <email@example.com>,
Emily Shaffer <firstname.lastname@example.org>,
git <email@example.com>, Taylor Blau <firstname.lastname@example.org>
Subject: Re: RFC - Git Developer Blog
Date: Wed, 7 Aug 2019 13:07:35 -0400 [thread overview]
Message-ID: <20190807170735.GA61464@syl.local> (raw)
On Tue, Aug 06, 2019 at 08:19:15AM -0400, Derrick Stolee wrote:
> On 8/6/2019 12:52 AM, Andrew Ardill wrote:
> > On Tue, 6 Aug 2019 at 11:51, Emily Shaffer <email@example.com> wrote:
> >> Are folks interested in writing and reviewing this kind of content?
> I am interested in writing and reviewing! Here are some topics I am
> interested in writing:
> * Updates to the commit-graph feature
> * What is a multi-pack-index and what is it for?
> * Git at Scale: What makes a repo big, and how to avoid it?
> * Advanced Git config settings
> Here are some topics I'd be interested in seeing in the wild
> (and was considering writing them myself if I didn't see them elsewhere):
> * Partial clone: what, why, and how?
> * Life cycle of a patch series
> * Crafting perfect patches with interactive add and rebase
> It would also be helpful to have a post for every major release
> highlighting new features and giving users examples of how to use them.
> Taylor has been writing these on the GitHub blog , but maybe he
> would be interested in writing them for this new venue?
>  https://github.blog/2019-06-07-highlights-from-git-2-22/
Yes, I generally try and publish a blog post once-per-release, and
generally with the following two goals in mind:
- talk about and publicize some of the new features in the latest
release (or releases, if I've missed a blog post or two)
- share some interesting tidbits about existing features.
I think it would be good to have these blog posts in both places, should
this proposal materialize. I would have to ask about whether or not
GitHub would be comfortable about cross-posting to a new venue, and I'd
be happy to raise the question when it comes up.
next prev parent reply other threads:[~2019-08-07 17:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 1:49 RFC - Git Developer Blog Emily Shaffer
2019-08-06 3:33 ` Junio C Hamano
2019-08-06 4:59 ` Christian Couder
2019-08-06 13:27 ` Jeff King
2019-08-06 21:07 ` Emily Shaffer
2019-08-07 17:00 ` Taylor Blau
2019-08-06 4:52 ` Andrew Ardill
2019-08-06 12:19 ` Derrick Stolee
2019-08-06 21:00 ` Emily Shaffer
2019-08-07 17:12 ` Taylor Blau
2019-08-07 17:07 ` Taylor Blau [this message]
2019-08-07 17:15 ` Junio C Hamano
2019-08-07 17:44 ` Taylor Blau
2019-08-06 13:20 ` Jeff King
2019-08-06 20:49 ` Emily Shaffer
2019-09-13 13:29 ` James Ramsay
2019-09-13 14:05 ` pedro rijo
2019-09-17 19:22 ` James Ramsay
2019-09-17 19:32 ` Emily Shaffer
2019-09-17 19:39 ` pedro rijo
2019-10-23 22:36 ` James Ramsay
2019-10-23 23:48 ` Jeff King
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:
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 \
* 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
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).