On 8/18/24 4:45 PM, shynur . wrote:
Hi, Chet.
I'm a beginner with Bash and recently stumbled upon the
Bash code repository (specifically the 'devel' branch).
I noticed that almost every commit includes thousands of
lines of changes.
Not really.
Out of curiosity, I randomly clicked on one of
On Monday, August 19, 2024, Koichi Murase wrote:
>
> One can put " diff=no" in .git/info/attributes to
> ignore these files in `git diff'.
This is a very good idea. Marking auto-generated files as binary in
/.gitattributes would address OP's concerns without changing how Bash is
built.
--
Oğu
> ... but that would increase the "build toolset" that
> everyone would have to install ...
This doesn't make much sense unless every other program
is built the same way. (A stark counterexample is Emacs.)
IOW, that wouldn't increase the "build toolset" much
because there probably be
2024年8月20日(火) 5:52 Koichi Murase :
> 2024年8月20日(火) 2:25 Martin D Kealey :
> > Perhaps a compromise would be to put the documentation in a directory
> > that's not inside the source code directory, so it's easier to `git diff`
> > just one or the other. (In practice, that would mean moving some of
2024年8月20日(火) 2:25 Martin D Kealey :
> Perhaps a compromise would be to put the documentation in a directory
> that's not inside the source code directory, so it's easier to `git diff`
> just one or the other. (In practice, that would mean moving some of the
> code into a new subdirectory.)
One c
On Mon, 19 Aug 2024 at 06:45, shynur . wrote:
> I believe these output files should be added to `.gitignore` and generated
> during the `make` process.
Not doing so is deliberate in some cases.
In an ideal world, yes they should be generated during `make`, but that
would increase the "build to
