Re: [Libcdio-devel] [PATCH] Fix gcc warnings

2023-03-26 Thread Thomas Schmitt
Hi, Rocky Bernstein wrote: > There is no way you can mess up in git, because history is saved by default > for *everyone. *And specifically I have a copy. I still see the opportunity for a race condition in the time window between pull and push. What happens if somebody else pushed a modified mas

Re: [Libcdio-devel] [PATCH] Fix gcc warnings

2023-03-26 Thread Mario Đanić
Hopefully you meant NO stress on him, we dont want him stressed out :D On Fri, 24 Mar 2023 at 00:08, Rocky Bernstein wrote: > On Thu, Mar 23, 2023 at 5:13 PM Thomas Schmitt wrote: > > > Hi, > > > > Rocky Bernstein wrote: > > > I was thinking that Pete would do the merge since he also has commit

Re: [Libcdio-devel] [PATCH] Fix gcc warnings

2023-03-26 Thread Mario Đanić
Rebase or merge. There are always ways :) On Sun, 26 Mar 2023 at 12:57, Thomas Schmitt wrote: > Hi, > > Rocky Bernstein wrote: > > There is no way you can mess up in git, because history is saved by > default > > for *everyone. *And specifically I have a copy. > > I still see the opportunity for

Re: [Libcdio-devel] [PATCH] Fix gcc warnings

2023-03-26 Thread Rocky Bernstein
On Sun, Mar 26, 2023 at 6:57 AM Thomas Schmitt wrote: > Hi, > > Rocky Bernstein wrote: > > There is no way you can mess up in git, because history is saved by > default > > for *everyone. *And specifically I have a copy. > > I still see the opportunity for a race condition in the time window > be

Re: [Libcdio-devel] [PATCH] Fix gcc warnings

2023-03-26 Thread Rocky Bernstein
On Sun, Mar 26, 2023 at 7:08 AM Mario Đanić wrote: > Hopefully you meant NO stress on him, we dont want him stressed out :D > Yes, you are correct: I meant NO stress. I am sorry for the stress this typo may have caused. > On Fri, 24 Mar 2023 at 00:08, Rocky Bernstein wrote: > > > On Thu, Mar

Re: [Libcdio-devel] [PATCH] Fix gcc warnings

2023-03-26 Thread Rocky Bernstein
On Sun, Mar 26, 2023 at 7:08 AM Mario Đanić wrote: > Rebase or merge. There are always ways :) > I never suggested this was the only way. I wrote that this was *a *command-line way (with a misspelling of "an" for "a") of what *might *be done. There are numerous other ways as well, and some of th

Re: [Libcdio-devel] [PATCH] Fix gcc warnings

2023-03-26 Thread Thomas Schmitt
Hi, Rocky Bernstein wrote: > > In other words, this is supposed to be a stress on you, we want you to > > succeed. Mario Đanić wrote: > Hopefully you meant NO stress on him, we dont want him stressed out :D Good to see that the younger generation cares for the blood pressure of us babyboomers. :

Re: [Libcdio-devel] [PATCH] Fix gcc warnings

2023-03-26 Thread Rocky Bernstein
It looks like everything went as expected. You did this like a pro! I have checked the changes and ran the usual test without problems. However I have since pushed another small administrative change to configure.ac because automake and autoconf now want things to be done differently. More work i

Re: [Libcdio-devel] CD-Text support for macOS and Windows

2023-03-26 Thread Rocky Bernstein
On Fri, Mar 24, 2023 at 3:58 AM Rocky Bernstein wrote: > Thanks for the macOS patches. I will probably try the Windows code this > weekend. > For what it is worth, I was able to build the current master on Windows 10 pro and Msys2. I suspect though that master doesn't have Robert's latest patch