On Mon, Jan 13, 2020 at 01:12:15PM -0500, Eric S. Raymond wrote:
> Jonathan Wakely :
> > Email the patches to gcc-patches@gcc.gnu.org, that's how things get
> > merged.
> >
> > We're not looking to change any workflows now.
>
> Roger that.
>
> Once the dust from the conversion has settled, thoug
On 19/01/20 20:06 -0700, Sandra Loosemore wrote:
On 1/13/20 9:12 AM, Joseph Myers wrote:
On Mon, 13 Jan 2020, Sandra Loosemore wrote:
On 1/13/20 7:02 AM, Eric S. Raymond wrote:
Clean up references to SVN in in the GCC docs, redirecting to Git
documentation as appropriate.
This is OK, althou
On 1/13/20 9:12 AM, Joseph Myers wrote:
On Mon, 13 Jan 2020, Sandra Loosemore wrote:
On 1/13/20 7:02 AM, Eric S. Raymond wrote:
Clean up references to SVN in in the GCC docs, redirecting to Git
documentation as appropriate.
This is OK, although the set of changes for the libstdc++ manual lik
On 13/01/20 09:02 -0500, Eric S. Raymond wrote:
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index b4bf333e26a..21c312dce35 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -34,9 +34,8 @@
clauses 20 through 33 and annex D (prior to t
On Mon, 13 Jan 2020, Jonathan Wakely wrote:
> Here's what I've committed to releases/gcc-9, I'll do something
> similar for gcc-8.
Cool, thank you.
That was a good catch, even without the conversion to GIT; I'll
see that I'll contribute to the conversion on the wwwdocs side
over the coming even
Jonathan Wakely :
> Email the patches to gcc-patches@gcc.gnu.org, that's how things get
> merged.
>
> We're not looking to change any workflows now.
Roger that.
Once the dust from the conversion has settled, though, there is a
related issue I intend to bring up on the main list.
You've only col
On 13/01/20 12:24 -0500, Eric S. Raymond wrote:
Joseph Myers :
I think you'll need to commit this for Eric (using --author= to set the
git author, whenever you commit a patch for someone else). The libstdc++
maintainers can probably handle regenerating the HTML version of the
libstdc++ document
Joseph Myers :
> I think you'll need to commit this for Eric (using --author= to set the
> git author, whenever you commit a patch for someone else). The libstdc++
> maintainers can probably handle regenerating the HTML version of the
> libstdc++ documentation.
I'm hesitant to request push acc
On 13/01/20 16:21 +, Jonathan Wakely wrote:
On 13/01/20 09:09 -0700, Sandra Loosemore wrote:
On 1/13/20 7:02 AM, Eric S. Raymond wrote:
Clean up references to SVN in in the GCC docs, redirecting to Git
documentation as appropriate.
This is OK, although the set of changes for the libstdc++
On 13/01/20 09:09 -0700, Sandra Loosemore wrote:
On 1/13/20 7:02 AM, Eric S. Raymond wrote:
Clean up references to SVN in in the GCC docs, redirecting to Git
documentation as appropriate.
This is OK, although the set of changes for the libstdc++ manual like
this gave me pause:
diff --git a
On Mon, 13 Jan 2020, Sandra Loosemore wrote:
> On 1/13/20 7:02 AM, Eric S. Raymond wrote:
> > Clean up references to SVN in in the GCC docs, redirecting to Git
> > documentation as appropriate.
>
> This is OK, although the set of changes for the libstdc++ manual like this
> gave me pause:
I thin
On 1/13/20 7:02 AM, Eric S. Raymond wrote:
Clean up references to SVN in in the GCC docs, redirecting to Git
documentation as appropriate.
This is OK, although the set of changes for the libstdc++ manual like
this gave me pause:
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
b
Clean up references to SVN in in the GCC docs, redirecting to Git
documentation as appropriate.
Where references to "the source code repository" rather than a
specific VCS make sensxse, I have used them. You might, after
all, change VCSes again someday.
I have not modified either generated HTML f
13 matches
Mail list logo
