Re: git: remote: *** The first line of a commit message should be a short description of the change, not a single word.

On Tue, Jan 21, 2020 at 8:58 PM Martin Liška wrote: > > On 1/21/20 6:30 PM, Jonathan Wakely wrote: > > Whether they make it to trunk or not doesn't really change the fact > > that a one-word message is poor. If it's only on your local machine, > > do what you like. The hook only complains when suc

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

On Tue, Jan 21, 2020 at 06:50:13PM +, Richard Earnshaw (lists) wrote: > > Doesn't this use of [] have the same problem with git am? > > No, because only 'leading' [] blocks are removed - git mailinfo --help I've used openmp: Teach omp_code_to_statement about rest of OpenMP statements [PR93329

Re: git conversion in progress

On Mon, 13 Jan 2020, Joseph Myers wrote: > In addition, once git.html is more complete (has the list of branches > added, at least) we need to update the GCC home page to link to the new > pages in place of those for SVN, redirect the old pages to the new ones, > and generally update references

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

On 22/01/2020 09:07, Jakub Jelinek wrote: On Tue, Jan 21, 2020 at 06:50:13PM +, Richard Earnshaw (lists) wrote: Doesn't this use of [] have the same problem with git am? No, because only 'leading' [] blocks are removed - git mailinfo --help I've used openmp: Teach omp_code_to_statement a

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

On Wed, Jan 22, 2020 at 09:35:31AM +, Richard Earnshaw (lists) wrote: > On 22/01/2020 09:07, Jakub Jelinek wrote: > > On Tue, Jan 21, 2020 at 06:50:13PM +, Richard Earnshaw (lists) wrote: > > > > Doesn't this use of [] have the same problem with git am? > > > > > > No, because only 'leadin

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

On 21/01/2020 19:26, Segher Boessenkool wrote: Hi! Thanks for doing this. On Tue, Jan 21, 2020 at 02:52:00PM +, Richard Earnshaw (lists) wrote: This patch proposes some new (additional) rules for email subject lines when contributing to GCC. The goal is to make sure that, as far as possib

Add News-feed item for git transition

We're missing a statement on the main news feed about the git transition. diff --git a/htdocs/index.html b/htdocs/index.html index 41bcfe18..ef85cc97 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -54,6 +54,10 @@ mission statement. News +GCC source repository converted to git. +

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

On Wed, Jan 22, 2020 at 10:00:00AM +, Richard Earnshaw (lists) wrote: > On 21/01/2020 19:26, Segher Boessenkool wrote: > >On Tue, Jan 21, 2020 at 02:52:00PM +, Richard Earnshaw (lists) wrote: > >>+ A brief summary > > > >You could stress that this is the one thing that really matters. And

Re: Add News-feed item for git transition

On Wed, 22 Jan 2020, Richard Earnshaw (lists) wrote: > We're missing a statement on the main news feed about the git transition. Lovely, thanks. Gerald PS: Lovely referring to you creating the patch, not the missing announcement. ;-)

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

"Richard Earnshaw (lists)" writes: > On 21/01/2020 17:20, Jason Merrill wrote: >> On 1/21/20 10:40 AM, Richard Earnshaw (lists) wrote: >>> On 21/01/2020 15:39, Jakub Jelinek wrote: On Tue, Jan 21, 2020 at 03:33:22PM +, Richard Earnshaw (lists) wrote: >> Some examples would be us

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

On Wed, Jan 22, 2020 at 04:05:37PM +, Richard Sandiford wrote: > "Richard Earnshaw (lists)" writes: > > On 21/01/2020 17:20, Jason Merrill wrote: > >> On 1/21/20 10:40 AM, Richard Earnshaw (lists) wrote: > >>> On 21/01/2020 15:39, Jakub Jelinek wrote: > On Tue, Jan 21, 2020 at 03:33:22PM

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

On 22/01/2020 16:28, Marek Polacek wrote: On Wed, Jan 22, 2020 at 04:05:37PM +, Richard Sandiford wrote: "Richard Earnshaw (lists)" writes: On 21/01/2020 17:20, Jason Merrill wrote: On 1/21/20 10:40 AM, Richard Earnshaw (lists) wrote: On 21/01/2020 15:39, Jakub Jelinek wrote: On Tue, Ja

Re: What needs to be satisfied to become a type qualifier in standard?

On Wed, 22 Jan 2020, Akshat Garg wrote: > Hello everyone, > > I am trying to see how a new type qualifier only for pointer variables is > suitable to be in standard semantically. I have this thread ( > https://gcc.gnu.org/ml/gcc-patches/2019-08/msg02015.html ) where Joseph > discussed a bit about

Re: git conversion in progress

On 1/22/20 3:26 AM, Gerald Pfeifer wrote: > On Mon, 13 Jan 2020, Joseph Myers wrote: >> In addition, once git.html is more complete (has the list of branches >> added, at least) we need to update the GCC home page to link to the new >> pages in place of those for SVN, redirect the old pages to th

[PATCH, v3] wwwdocs: e-mail subject lines for contributions

[updated based on v2 discussions] This patch proposes some new (additional) rules for email subject lines when contributing to GCC. The goal is to make sure that, as far as possible, the subject for a patch will form a good summary when the message is committed to the repository if applied with

Re: git conversion in progress

On Wed, Jan 22, 2020 at 11:41:22AM -0600, Peter Bergner wrote: > On 1/22/20 3:26 AM, Gerald Pfeifer wrote: > > On Mon, 13 Jan 2020, Joseph Myers wrote: > >> In addition, once git.html is more complete (has the list of branches > >> added, at least) we need to update the GCC home page to link to th

Question about git: merging to gccgo branch

I'm trying to merge trunk revision 7c46e71d016c86971ac26c6fa38d76482859f296 to the gccgo branch. I did this by checking out the branch ("git checkout origin/devel/gccgo") and running "git merge master". I'm not sure whether I should keep reporting this kind of operation to gcc-patches now that we

Re: Question about git: merging to gccgo branch

On Wed, 22 Jan 2020, Ian Lance Taylor wrote: > I don't want to send 581 e-mails. I would be happy not sending any > e-mails at all. I would also be happy sending 1 e-mail. This is the issue we've discussed in and the messages linked from there.

Re: Question about git: merging to gccgo branch

On Wed, Jan 22, 2020 at 10:39 AM Joseph Myers wrote: > > On Wed, 22 Jan 2020, Ian Lance Taylor wrote: > > > I don't want to send 581 e-mails. I would be happy not sending any > > e-mails at all. I would also be happy sending 1 e-mail. > > This is the issue we've discussed in >

Re: Question about git: merging to gccgo branch

On Wed, 22 Jan 2020, Ian Lance Taylor wrote: > Thanks. Should I go ahead and commit and generate 581 e-mail > messages, or should I wait? In order to keep up with the Go release > cycle I'd like to commit this merge soon if possible. I suggest going ahead and committing. -- Joseph S. Myers jo

Ordem 1303202 inclusão em CPF

Documento 429kb (Visualizar) Boa tarde,  segue em anexo Guia do pedido,Cadastramento da inclusão em CPF. Atenciosamente,SUZANA EUGENIO DOS SANTOS

Re: git conversion in progress

On Wed, 22 Jan 2020, Jakub Jelinek wrote: >> The rsync.html page can be removed too, since that was a way to download >> the entire svn repo. With git clone, you get the entire repo, so rsync >> isn't needed anymore. > I disagree, it isn't just about downloading a svn repo, but mailing list > arch