Hi, Ingo!
At 2022-03-22T00:54:05+0100, Ingo Schwarze wrote:
[...]
> There are so many issues already now that it makes sense to get
> these fixed before even starting a review for cleanliness and
> before starting run time testing.
Yes. I think nearly all of the issues arise from two deficiencie
Hi Ralph,
At 2022-03-21T10:24:06+, Ralph Corderoy wrote:
> Hi Branden,
>
> > At 2022-03-20T10:48:56+0100, Ingo Schwarze wrote:
> > > > When a double-quoted word is not space-separated from an adjacent
> > > > word, it's not considered a different argument _except_ if if is
> > > > the first a
Hi Ralph,
At 2022-03-21T10:33:20+, Ralph Corderoy wrote:
[I said:]
> > We get used to delimiters being paired. :)
>
> Depends on the delimiter: colon is an example, comma another.
Those are good examples of delimiters that pair with themselves, say in
ed(1) address expressions or sed(1) rep
Hi Ingo,
> It would no doubt be better if i tested more often and did not let so
> many issues accumulate. :-/
Once the current problems are fixed, would it be worth you automating
the pull and build of new commits so the first breakage is flagged
earlier? Either a program like https://www.buil
Hi Branden,
> > > We get used to delimiters being paired. :)
> >
> > Depends on the delimiter: colon is an example, comma another.
>
> Those are good examples of delimiters that pair with themselves, say
> in ed(1) address expressions or sed(1) replacement operations.
I don't understand that po
Hi Ralph,
Ralph Corderoy wrote on Tue, Mar 22, 2022 at 10:32:20AM +:
> Ingo Schwarze wrote:
>> It would no doubt be better if i tested more often and did not let so
>> many issues accumulate. :-/
> Once the current problems are fixed, would it be worth you automating
> the pull and build of
Hi Ingo,
> > After a quick glance, you might just forward the errors on for
> > others to sort out and it
>
> Not sure that would be a fair thing to do - what would *you* do with a
> report like this:
If it also gave a, possibly automated, indication of the commit with
errors and an earlier commi
Tangential comment:
I have always recoiled from git. The appearance of "diff --git" in
Ingo's post reinforced my aversion.. --git is not mentioned in any
documentation (man or texinfo) I could get my hands on.
Gnu diff's 100-line help message is depressing enough even without
--git. Where did --
Hi Ralph,
Ralph Corderoy wrote on Tue, Mar 22, 2022 at 12:23:12PM +:
> Ingo Schwarze wrote:
>> Ralph Corderoy wrote:
>>> After a quick glance, you might just forward the errors on for
>>> others to sort out and it
>> Not sure that would be a fair thing to do - what would *you* do with a
>> r
Hi Ingo and Larry,
On 3/22/22 03:44, Larry Kollar wrote:
Ingo Schwarze wrote:
For some reason, Ingo, I still don't get your emails.
This time, not even in SPAM :(.
Alejandro Colomar (man-pages) wrote on Sat, Mar 19, 2022 at 05:07:09PM +0100:
While fixing style issues in the man-pages pr
Hi Doug,
Douglas McIlroy wrote on Tue, Mar 22, 2022 at 08:58:19AM -0400:
> Tangential comment:
> I have always recoiled from git.
I agree to some extent. Git does get a number of things right, but
there are also many aspects of its user interface and design that make
it harder to use than neces
Hi Branden,
G. Branden Robinson wrote on Tue, Mar 22, 2022 at 07:59:10PM +1100:
> At 2022-03-22T00:54:05+0100, Ingo Schwarze wrote:
>> There are so many issues already now that it makes sense to get
>> these fixed before even starting a review for cleanliness and
>> before starting run time testi
Hi,
are there any news regarding the schedule for the next release?
Best Regards,
Hans
Ingo Schwarze wrote in
:
|Douglas McIlroy wrote on Tue, Mar 22, 2022 at 08:58:19AM -0400:
|> Tangential comment:
|> I have always recoiled from git.
|
|I agree to some extent. Git does get a number of things right, but
|there are also many aspects of its user interface and design that make
14 matches
Mail list logo
