On 21/01/2020, 21:29, "Rich Persaud" wrote:
On Jan 21, 2020, at 15:58, Marek Marczykowski-Górecki
wrote:
>
> On Wed, Jan 15, 2020 at 04:57:29PM -0500, Rich Persaud wrote:
On Jan 14, 2020, at 21:42, Marek Marczykowski-Górecki
wrote:
>>> Since we have those generate
On Jan 21, 2020, at 15:58, Marek Marczykowski-Górecki
wrote:
>
> On Wed, Jan 15, 2020 at 04:57:29PM -0500, Rich Persaud wrote:
On Jan 14, 2020, at 21:42, Marek Marczykowski-Górecki
wrote:
>>> Since we have those generated files committed to the repo (why?!),
>>> update them after c
On Wed, Jan 15, 2020 at 04:57:29PM -0500, Rich Persaud wrote:
> > On Jan 14, 2020, at 21:42, Marek Marczykowski-Górecki
> > wrote:
> > Since we have those generated files committed to the repo (why?!),
> > update them after changing configure.ac.
>
> Is there any reason not to remove the genera
> On Jan 14, 2020, at 21:42, Marek Marczykowski-Górecki
> wrote:
> Since we have those generated files committed to the repo (why?!),
> update them after changing configure.ac.
Is there any reason not to remove the generated configure files? A developer
using generated files on system B would
Since we have those generated files committed to the repo (why?!),
update them after changing configure.ac.
Signed-off-by: Marek Marczykowski-Górecki
---
configure | 14 +-
docs/configure| 14 +-
stubdom/configure | 14 +-
tools/config.h.in | 3 ++
