On Mon, Dec 7, 2020 at 12:46 AM Paul Smith wrote:
> Maybe if you described the thing you were trying to accomplish or
> understand, and what about the documentation made this difficult, we
> could come up with a practical example or improve the documentation.
Yes, I totally agree with you about
On Thu, 2020-12-03 at 15:04 +0300, Dmitry wrote:
> > > It'll be very good to have some examples with explanations in the
> > > docs.
> > Maybe so. Concrete suggestions are easy to discuss, like:
>
> I think this example would saved me a lot of time.
>
> make -f mkfile
>
> content of mkfile:
>
On Thu, Dec 3, 2020 at 4:07 PM wrote:
> With all respect, yours is is a baseless complaint - please complain to your
> English teacher instead.
With all respect, why do you choose the most negligible subject and
show me your dominance, professor?
What about the other two complaints? Are they
> > default rules, in which case the documentation could mention SCCS and RCS
> > specifically without becoming a maintenance burden. Reading the original
> > discussion, though, perhaps the more useful clarification would have been
> > to make it explicit that Make has
t Make has default, built-in make rules, the ones from
> https://www.gnu.org/software/make/manual/make.html#Catalogue-of-Rules.
>
>
> From: Bug-make on behalf of
> Dmitry
> Sent: Monday, November 30, 2020 09:51
> To: bug-make@gnu.o
ttps://www.gnu.org/software/make/manual/make.html#Catalogue-of-Rules.
From: Bug-make on behalf of
Dmitry
Sent: Monday, November 30, 2020 09:51
To: bug-make@gnu.org
Subject: notes about make docs p 3.5
* EXTERNAL EMAIL *
Hello, I'm reading GNU make docs and
Hello, I'm reading GNU make docs and had troubles with understanding
paragraph 3.5 .
These are some problems which I encountered:
1) make starts with a clean slate-> make starts with a clean sTate
2) It was difficult to understand how make remade makefiles without examples.
There is discussion
