On Fri, Jul 20, 2018 at 11:04 PM Joseph Myers wrote:
>
> On Thu, 5 Jul 2018, Aldy Hernandez wrote:
>
> > However, even if you could "git log --grep" the commit messages, I assume
> > your
> > current use is grepping for function names and such, right? Being able to
> > grep
> > a commit message
Hi,
This is nothing to do with undefined behaviour, but a matter of
scheduling of effects that are visible in different circumstances. In
particular, i and j are declared in a way that tells the compiler that
the compiler, in its current thread of execution has full control of
them. The compiler
On Mon, Jul 23, 2018 at 11:52:03AM +0200, Richard Biener wrote:
> Does -L "work" with codebases that become more and more C++? I do realize
> that grepping ChangeLogs gets more difficult here as well given there are no
> clear rules how to "mangle" C++ function/entity names in ChangeLog entries.
>
Hi!
On Mon, Jul 23, 2018 at 12:36:50PM +0200, David Brown wrote:
> This is nothing to do with undefined behaviour, but a matter of
> scheduling of effects that are visible in different circumstances. In
> particular, i and j are declared in a way that tells the compiler that
> the compiler, in it
On Mon, 23 Jul 2018, Segher Boessenkool wrote:
> For example for .md files you can use
>
> [diff "md"]
> xfuncname = "^\\(define.*$"
>
> in your local clone's .git/config
>
> and
>
> *.md diff=md
>
> in .gitattributes (somewhere in the source tree).
Not necessarily in the source tre
On 21/07/18 03:04, Eric S. Raymond wrote:
> That light at the end of the tunnel turned out to be an oncoming train.
>
> Until recently I thought the conversion was near finished. I'd had
> verified clean conversions across trunk and all branches, except for
> one screwed-up branch that the managem
On Sat, Jul 21, 2018 at 1:39 PM Eric S. Raymond
wrote:
>
> On Sat, Jul 21, 2018 at 09:26:10AM +0200, Richard Biener wrote:
> > Can you summarize what is wrong with our current git mirror which was IIRC
> > created by git-svn importing?
>
> git-svn tends to do subtle danage damage to the back his
On Tue, 17 Jul 2018, Martin Liška wrote:
> I've recently touched AWK option generate machinery and it's quite
> unpleasant to make any adjustments. My question is simple: can we
> starting using a scripting language like Python and replace usage of the
> AWK scripts? It's probably question for
On Tue, 17 Jul 2018, Paul Koning wrote:
> That reveals some things but nothing jumps out at me. However... pdp11
> is an a.out target, not an ELF target. Would that explain the problem?
> If yes, is there a workaround (short of implementing ELF)?
As there are hardly any targets left without
On Wed, 18 Jul 2018, David Malcolm wrote:
> Python 3.3 reintroduced the 'u' prefix for unicode string literals (PEP
> 414), which makes it much easier to write scripts that work with both
> 2.* and 3.*. Python 3.3 is almost 6 years old.
I can't see u'' as of any relevance to .opt parsing. Both
> On Jul 23, 2018, at 10:21 AM, Joseph Myers wrote:
>
> On Tue, 17 Jul 2018, Paul Koning wrote:
>
>> That reveals some things but nothing jumps out at me. However... pdp11
>> is an a.out target, not an ELF target. Would that explain the problem?
>> If yes, is there a workaround (short of
On Mon, Jul 23, 2018 at 04:03:31PM +0300, Alexander Monakov wrote:
> Not necessarily in the source tree: individual users can put that into their
> $XDG_CONFIG_HOME/git/attributes or $HOME/.config/git/attributes.
And then that user has *all* .md files treated as GCC machine description
files. But
On 7/23/18, Segher Boessenkool wrote:
> On Mon, Jul 23, 2018 at 04:03:31PM +0300, Alexander Monakov wrote:
>> Not necessarily in the source tree: individual users can put that into
>> their
>> $XDG_CONFIG_HOME/git/attributes or $HOME/.config/git/attributes.
>
> And then that user has *all* .md fil
On Mon, 23 Jul 2018, Richard Biener wrote:
> Does -L "work" with codebases that become more and more C++? I do realize
Well, you can specify an arbitrary regular expression for your funcname
line with -L if you need to.
--
Joseph S. Myers
jos...@codesourcery.com
On Mon, 23 Jul 2018, Richard Earnshaw (lists) wrote:
> So traditional git bisect is inherently serial, but we can be more
> creative here, surely. A single run halves the search space each time.
> But three machines working together can split it into 4 each run, 7
> machines into 8, etc. You don
On 07/23/2018 08:53 AM, Joseph Myers wrote:
> On Mon, 23 Jul 2018, Richard Earnshaw (lists) wrote:
>
>> So traditional git bisect is inherently serial, but we can be more
>> creative here, surely. A single run halves the search space each time.
>> But three machines working together can split it
> On Jul 23, 2018, at 12:21 PM, Jeff Law wrote:
>
>>
> Hell, I'd live with doing a "reasonable effort" for the vast majority of
> our branches. Other than the trunk, active release branches and a few
> active development branches I don't think we really care about 'em.
>
> jeff
There are t
On 07/23/2018 10:29 AM, Paul Koning wrote:
>
>
>> On Jul 23, 2018, at 12:21 PM, Jeff Law wrote:
>>
>>>
>> Hell, I'd live with doing a "reasonable effort" for the vast majority of
>> our branches. Other than the trunk, active release branches and a few
>> active development branches I don't thin
On Mon, 23 Jul 2018, Jeff Law wrote:
> > There are two approaches to conversion: (1) convert what's active and
> > preserve the old system indefinitely for reference access; (2) convert
> > everything 100% so the old system can be retired.
> >
> > It seems that Eric has been trying for #2, whic
On Mon, Jul 23, 2018 at 02:48:12PM +, Joseph Myers wrote:
> On Mon, 23 Jul 2018, Richard Biener wrote:
>
> > Does -L "work" with codebases that become more and more C++? I do realize
>
> Well, you can specify an arbitrary regular expression for your funcname
> line with -L if you need to.
20 matches
Mail list logo
