public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Sandra Loosemore <sandra@codesourcery.com>,
	fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 0/5] Fortran manual updates
Date: Tue, 2 Nov 2021 16:20:23 +0100	[thread overview]
Message-ID: <a59575fb-1505-3467-6642-c4ed00ad4dcb@suse.cz> (raw)
In-Reply-To: <1760a024-901e-fa4e-067d-5d70e2cbd762@codesourcery.com>

On 11/2/21 15:48, Sandra Loosemore wrote:
> On 11/2/21 2:51 AM, Martin Liška wrote:
>> On 11/2/21 00:56, Sandra Loosemore wrote:
>>> I'll wait a couple days before committing these patches, in case
>>> anybody wants to give some feedback, especially on technical issues.
>>
>> Hello.
>>
>> Appreciate the work you did, but the patchset will cause quite some conflicts
>> in the prepared Sphinx migration patch I've sent to the mailing list :/
>> Anyway, I will rebase my patches. For the future, are you planning doing similar
>> documentation reorganization for a manual? Based on discussion with Gerald, I hope
>> we can finish the transition before the end of this year.
> 
> My understanding was that, if this conversion is indeed going to happen, it's going to be automated by scripts?

Exactly, but the conversion needs some manual post-processing that I've already done.

>  I hadn't seen any discussion of it on the list for months and thought the whole idea was on hold or scrapped, since it hasn't happened yet.

There was almost no response, so that's why I contacted Gerald about help.

> In any case it does not seem reasonable to freeze the current Texinfo docs for months while waiting for it to happen, especially as we are heading into the end of the release cycle and people are finishing up changes and new features they need to document.

Sure, I can easily rebase normal changes, but you are suggesting a complete redesign/renaming. It's going to take me some time,
but I'll rebase my patches.

Thanks for understanding,
Martin

> 
> -Sandra


  reply	other threads:[~2021-11-02 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 23:56 Sandra Loosemore
2021-11-01 23:56 ` [PATCH 1/5] Fortran manual: Combine standard conformance docs in one place Sandra Loosemore
2021-11-01 23:57 ` [PATCH 2/5] Fortran manual: Revise introductory chapter Sandra Loosemore
2021-11-01 23:57 ` [PATCH 3/5] Fortran manual: Update section on Interoperability with C Sandra Loosemore
2021-11-01 23:57 ` [PATCH 4/5] Fortran manual: Update miscellaneous references to old standard versions Sandra Loosemore
2021-11-02  8:51 ` [PATCH 0/5] Fortran manual updates Martin Liška
2021-11-02 14:48   ` Sandra Loosemore
2021-11-02 15:20     ` Martin Liška [this message]
2021-11-02 15:56       ` Sandra Loosemore
2021-11-02 20:32         ` Damian Rouson
2021-11-04 10:04         ` Martin Liška
2021-11-04 11:16           ` Richard Biener

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=a59575fb-1505-3467-6642-c4ed00ad4dcb@suse.cz \
    --to=mliska@suse.cz \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sandra@codesourcery.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.
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).