From: Christian Couder <christian.couder@gmail.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [RFH] Request for Git Merge 2017 impressions for Git Rev News
Date: Mon, 13 Feb 2017 22:27:26 +0100 [thread overview]
Message-ID: <CAP8UFD3N0Qme51T-dWs5DxL-FowEBaFBzHCAi=U3UG1Sbh4O7g@mail.gmail.com> (raw)
In-Reply-To: <8b6e998d-2bea-924b-42e3-936dcd9a2995@gmail.com>
Hi,
On Sat, Feb 11, 2017 at 5:33 PM, Jakub Narębski <jnareb@gmail.com> wrote:
> Hello,
>
> Git Rev News #24 is planned to be released on February 15. It is meant
> to cover what happened during the month of January 2017 (and earely
> February 2017) and the Git Merge 2017 conference that happened on
> February 2nd and 3rd 2017.
Yeah, I would have liked to release Git Rev News #24 on February 15
but I was busy and tired this week end, so let it be on Wednesday
February 22.
> 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-24.md
>
> I would like to ask everyone who attended the conference (and the
> GitMerge 2017 Contributors’s Summit day before it), or watched it live
> at http://git-merge.com/watch to write his or her impressions.
>
> You can contribute either by replying to this email, or by editing the
> above page on GitHub and sending a pull request, or by commenting on
> the following GitHub issue about Git Rev News 24:
>
> https://github.com/git/git.github.io/issues/221
>
> If you prefer to post on your own blog (or if you have did it
> already), please send an URL.
Yeah, any material (link, short impression, article, ...) would be very nice.
Thanks Jakub for the links you already added to the draft, by the way!
> P.S. I wonder if there should be not a separate section on
> https://git.github.io/ about recollection from various Git-related
> events, with Git Merge 2017 as the first one. This way we can wait
> for later response, and incorporate videos and slides from events, as
> they begin to be available.
Jakub, if you are willing to create and maintain this section, that
would be great!
> P.P.S. Please distribute this information more widely.
Thanks,
Christian.
prev parent reply other threads:[~2017-02-13 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 16:33 [RFH] Request for Git Merge 2017 impressions for Git Rev News Jakub Narębski
2017-02-13 21:27 ` 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='CAP8UFD3N0Qme51T-dWs5DxL-FowEBaFBzHCAi=U3UG1Sbh4O7g@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).