Re: git conversion in progress

On Thu, 16 Jan 2020, Jonathan Wakely wrote: > On Thu, 16 Jan 2020 at 09:55, Georg-Johann Lay wrote: >> Hi, the front page reads "Our sources are readily and freely available >> via SVN...", similar recommendation for SVN in > Yes, it's been said more than once that the web pages will be updated >

Re: 1-800-GIT-HELP: Fixing a commit message?

On Thu, Jan 16, 2020 at 07:51:37PM +0100, Gerald Pfeifer wrote: > It turns out I fumbled the commit message on the commit below to wwwdocs. > > Instead of > Redirect cvswrite.html to gitwrite.html instead of svnwrite.html. > I committed this with a message of > Redirect cvs.html to git.h

1-800-GIT-HELP: Fixing a commit message?

It turns out I fumbled the commit message on the commit below to wwwdocs. Instead of Redirect cvswrite.html to gitwrite.html instead of svnwrite.html. I committed this with a message of Redirect cvs.html to git.html instead of svn.html. and pushed already. In CVS I could manually edit t

Re: PPC64 libmvec implementation of sincos

‐‐‐ Original Message ‐‐‐ On Wednesday, January 15, 2020 3:20 PM, GT wrote: > ‐‐‐ Original Message ‐‐‐ > On Thursday, January 9, 2020 8:42 AM, Richard Biener > richard.guent...@gmail.com wrote: > > > As for the other question for testing you probably want to provide a > > OMP si

Re: gcc-cvs mails for personal/vendor branches for merge commits

On Thu, 16 Jan 2020, Jakub Jelinek wrote: > Couldn't it be then per-branch setting, whether to mail even commits > that aren't new to the repository or not (like I understood it is already > possible to decide per-branch whether to send mails at all)? Feel free to add such suggestions to the issu

Re: gcc-cvs mails for personal/vendor branches for merge commits

On Thu, 16 Jan 2020, Joel Brobecker wrote: > emails are to be sent. This happens for instance when people used > development branches that they had silenced so as to avoid spamming > people. And because they have been rebasing their branch regularly, > the "merge" ended up being a fast-forward. An

Re: gcc-cvs mails for personal/vendor branches for merge commits

On Thu, Jan 16, 2020 at 02:15:21PM +, Richard Earnshaw (lists) wrote: > The alternative I suggested to Joseph yesterday was a separate mailing list > for all the personal and vendor commits. But I think that would need a > change to the hooks infrastructure. Would that solve it? We have arou

Re: GCC GSoC 2020: Call for mentors and project ideas

On 1/16/20 8:33 AM, Nathan Sidwell wrote: On 1/15/20 5:45 PM, Martin Jambor wrote: Therefore, first and foremost, I would like to ask all (moderately) seasoned GCC contributors to consider mentoring a student this year and ideally also come up with a project that they would like to lead.  I'

Re: gcc-cvs mails for personal/vendor branches for merge commits

On 16/01/2020 14:11, Jakub Jelinek wrote: On Thu, Jan 16, 2020 at 12:40:02PM +0100, Joel Brobecker wrote: I think there's a similar issue not just for merges but for non-fast-forward pushes as well. As a glibc example, consider and the

Re: gcc-cvs mails for personal/vendor branches for merge commits

On Thu, Jan 16, 2020 at 12:40:02PM +0100, Joel Brobecker wrote: > > I think there's a similar issue not just for merges but for > > non-fast-forward pushes as well. As a glibc example, consider > > and the long > > series of subsequent

Re: GCC GSoC 2020: Call for mentors and project ideas

On 1/15/20 5:45 PM, Martin Jambor wrote: Therefore, first and foremost, I would like to ask all (moderately) seasoned GCC contributors to consider mentoring a student this year and ideally also come up with a project that they would like to lead. I'm collecting proposal on our wiki page https:/

Re: gcc-cvs mails for personal/vendor branches for merge commits

> Joel, this is definitely a question for you; it's beyond my expertise in > the working of the hooks. The issue is that when a merge commit is > pushed, we only want mails for commits that are new *to the repository* - > not those that are already in the repository (accessible from some other

Re: git conversion in progress

On Thu, 16 Jan 2020 at 09:55, Georg-Johann Lay wrote: > > Am 11.01.20 um 02:18 schrieb Joseph Myers: > > I encourage people to continue to work on improving the documentation for > > using git with GCC > > Hi, the front page reads "Our sources are readily and freely available > via SVN...", simila

Re: git conversion in progress

Am 11.01.20 um 02:18 schrieb Joseph Myers: I encourage people to continue to work on improving the documentation for using git with GCC Hi, the front page reads "Our sources are readily and freely available via SVN...", similar recommendation for SVN in https://gcc.gnu.org/snapshots.html Jo