public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
* https://github.com/llvm/llvm-project/tree/master/pstl link broken
@ 2021-03-28 21:19 Gerald Pfeifer
  2021-03-28 21:23 ` Jonathan Wakely
  0 siblings, 1 reply; 6+ messages in thread
From: Gerald Pfeifer @ 2021-03-28 21:19 UTC (permalink / raw)
  To: libstdc++

Hi folks,

I noticed http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html
has a link to https://github.com/llvm/llvm-project/tree/master/pstl
which does not exist any more.

Would you mind having a look and updating (or removing) that link?

Thank you,
Gerald




^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: https://github.com/llvm/llvm-project/tree/master/pstl link broken
  2021-03-28 21:19 https://github.com/llvm/llvm-project/tree/master/pstl link broken Gerald Pfeifer
@ 2021-03-28 21:23 ` Jonathan Wakely
  2021-03-29 13:15   ` Jonathan Wakely
  0 siblings, 1 reply; 6+ messages in thread
From: Jonathan Wakely @ 2021-03-28 21:23 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: libstdc++

On Sun, 28 Mar 2021, 22:20 Gerald Pfeifer, <gerald@pfeifer.com> wrote:

> Hi folks,
>
> I noticed http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html
> has a link to https://github.com/llvm/llvm-project/tree/master/pstl
> which does not exist any more.
>
> Would you mind having a look and updating (or removing) that link?
>

They renamed the 'master' branch. I'll adjust the link tomorrow.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: https://github.com/llvm/llvm-project/tree/master/pstl link broken
  2021-03-28 21:23 ` Jonathan Wakely
@ 2021-03-29 13:15   ` Jonathan Wakely
  2023-01-15 21:22     ` Renaming git master? Gerald Pfeifer
  0 siblings, 1 reply; 6+ messages in thread
From: Jonathan Wakely @ 2021-03-29 13:15 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: libstdc++, gcc-patches

[-- Attachment #1: Type: text/plain, Size: 547 bytes --]

On 28/03/21 22:23 +0100, Jonathan Wakely via Libstdc++ wrote:
>On Sun, 28 Mar 2021, 22:20 Gerald Pfeifer, <gerald@pfeifer.com> wrote:
>
>> Hi folks,
>>
>> I noticed http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html
>> has a link to https://github.com/llvm/llvm-project/tree/master/pstl
>> which does not exist any more.
>>
>> Would you mind having a look and updating (or removing) that link?
>>
>
>They renamed the 'master' branch. I'll adjust the link tomorrow.

Done by this patch, pushed to master (which I think we should rename).



[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1178 bytes --]

commit e19afa0645f19287517a139c0428cfd1f3a63742
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Mar 29 14:13:01 2021

    libstdc++: Adjust link to PSTL upstream (again)
    
    The LLVM project renamed their default branch to 'main'.
    
    libstdc++-v3/ChangeLog:
    
            * doc/xml/manual/status_cxx2017.xml: Adjust link for PSTL.
            * doc/html/manual/status.html: Regenerate.

diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
index 7f64c47bdfe..11372bb28b3 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
@@ -1882,7 +1882,7 @@ since C++14 and the implementation is complete.
       <entry>28.4</entry>
       <entry>Parallel algorithms</entry>
       <entry/>
-      <entry>Using <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://github.com/llvm/llvm-project/tree/master/pstl">PSTL</link></entry>
+      <entry>Using <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://github.com/llvm/llvm-project/tree/main/pstl">PSTL</link></entry>
     </row>
     <row>
       <entry>28.5</entry>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Renaming git master?
  2021-03-29 13:15   ` Jonathan Wakely
@ 2023-01-15 21:22     ` Gerald Pfeifer
  2023-01-15 22:44       ` Jonathan Wakely
  2023-01-16 18:35       ` Joseph Myers
  0 siblings, 2 replies; 6+ messages in thread
From: Gerald Pfeifer @ 2023-01-15 21:22 UTC (permalink / raw)
  To: gcc, Jonathan Wakely; +Cc: libstdc++

[ gcc-patches -> gcc ]

On Mon, 29 Mar 2021, Jonathan Wakely wrote:
>> [LLVM] renamed the 'master' branch. I'll adjust the link tomorrow.
> Done by this patch, pushed to master (which I think we should rename).

Did I miss any discussions? Our documentation at 
  https://gcc.gnu.org/git.html
still refers to master (though, probably dating back to the SVN days there 
are quite a number of references to trunk, too).

`git branch -l` shows 
  master
  remotes/origin/HEAD -> origin/master
  remotes/origin/trunk


1. Is there something we may want to adjust in the Git repository?

2. How about https://gcc.gnu.org/git.html ? 

   (If someone tells me what to use instead of "master" I can propose a 
   patch.)
 
Gerald

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Renaming git master?
  2023-01-15 21:22     ` Renaming git master? Gerald Pfeifer
@ 2023-01-15 22:44       ` Jonathan Wakely
  2023-01-16 18:35       ` Joseph Myers
  1 sibling, 0 replies; 6+ messages in thread
From: Jonathan Wakely @ 2023-01-15 22:44 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: gcc, Jonathan Wakely, libstdc++

[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]

On Sun, 15 Jan 2023, 21:23 Gerald Pfeifer, <gerald@pfeifer.com> wrote:

> [ gcc-patches -> gcc ]
>
> On Mon, 29 Mar 2021, Jonathan Wakely wrote:
> >> [LLVM] renamed the 'master' branch. I'll adjust the link tomorrow.
> > Done by this patch, pushed to master (which I think we should rename).
>
> Did I miss any discussions?


I don't think so.

Our documentation at
>   https://gcc.gnu.org/git.html
> still refers to master (though, probably dating back to the SVN days there
> are quite a number of references to trunk, too).
>
> `git branch -l` shows
>   master
>   remotes/origin/HEAD -> origin/master
>   remotes/origin/trunk
>
>
> 1. Is there something we may want to adjust in the Git repository?
>

If we want to rename master, yes, we'd need changes to the repo on the
server.



> 2. How about https://gcc.gnu.org/git.html ?
>
>    (If someone tells me what to use instead of "master" I can propose a
>    patch.)
>


The new convention used by most projects (and the default on GitHub, and
offered as default by Git) is 'main'.

We could add 'main' as another symbolic ref for master, which is where we
already do for 'trunk'. That would allow people to choose whether to use
trunk or main, or keep using master (and existing configs would keep
working if not updated).

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Renaming git master?
  2023-01-15 21:22     ` Renaming git master? Gerald Pfeifer
  2023-01-15 22:44       ` Jonathan Wakely
@ 2023-01-16 18:35       ` Joseph Myers
  1 sibling, 0 replies; 6+ messages in thread
From: Joseph Myers @ 2023-01-16 18:35 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: gcc, Jonathan Wakely, libstdc++

On Sun, 15 Jan 2023, Gerald Pfeifer wrote:

>    (If someone tells me what to use instead of "master" I can propose a 
>    patch.)

If you wish to add additional symbolic-refs / make master into a 
symbolic-ref, please make sure to change hooks-bin, 
refs/meta/config:project.config and anything else required about the hooks 
to treat the new name the same as master, *before not after* adding the 
new name.

https://gcc.gnu.org/pipermail/gcc/2021-August/236953.html

-- 
Joseph S. Myers
joseph@codesourcery.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-01-16 18:35 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-28 21:19 https://github.com/llvm/llvm-project/tree/master/pstl link broken Gerald Pfeifer
2021-03-28 21:23 ` Jonathan Wakely
2021-03-29 13:15   ` Jonathan Wakely
2023-01-15 21:22     ` Renaming git master? Gerald Pfeifer
2023-01-15 22:44       ` Jonathan Wakely
2023-01-16 18:35       ` Joseph Myers

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).