From: Philip Oakley <philipoakley@iee.email>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
"Markus Jansen" <mja@jansen-preisler.de>,
"Jeff King" <peff@peff.net>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Josh Steadmon" <steadmon@google.com>,
"Han-Wen Nienhuys" <hanwen@google.com>,
"Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>,
"Junio C Hamano" <gitster@pobox.com>,
"Christian Couder" <christian.couder@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Draft of Git Rev News edition 79
Date: Thu, 30 Sep 2021 11:43:46 +0100 [thread overview]
Message-ID: <617f428d-2453-36f3-6abd-dbc7859e2a0c@iee.email> (raw)
In-Reply-To: <2882D89C-7CFF-4CCC-800A-B9A3E7533496@gmail.com>
Maybe it's the Github interface :-(
I edited the page on github, which said I didn't have direct edit
permission, but would create sone intermediary (can't remember what
exactly), and at the end it asked if I wanted to create a PR and I said
yes (clicked the green button).
Looks like it was a black hole of confusions.
I'll have a quick look (via my account) to see if I can see what happened.
Philip
On 30/09/2021 10:37, Kaartic Sivaraam wrote:
> Hi Philip,
>
>
> On 29 September 2021 6:01:12 pm IST, Philip Oakley <philipoakley@iee.email> wrote:
>> Added a couple of video links to the light reading. PR sent.
>>
> I'm trying to locate your PR at the following link but couldn't find it. Anything I missed?
> https://github.com/git/git.github.io/pulls?q=is%3Apr
>
next prev parent reply other threads:[~2021-09-30 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 12:36 Draft of Git Rev News edition 79 Christian Couder
2021-09-29 12:31 ` Philip Oakley
2021-09-30 9:37 ` Kaartic Sivaraam
2021-09-30 10:43 ` Philip Oakley [this message]
2021-09-30 10:56 ` Philip Oakley
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=617f428d-2453-36f3-6abd-dbc7859e2a0c@iee.email \
--to=philipoakley@iee.email \
--cc=Johannes.Schindelin@gmx.de \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hanwen@google.com \
--cc=jnareb@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=mja@jansen-preisler.de \
--cc=peff@peff.net \
--cc=steadmon@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).