Pregenerated files: repo freeze and discourse
Thomas.Doerfler at embedded-brains.de
Wed Aug 1 06:01:36 UTC 2012
just my two cents in this discussion:
Am 01.08.2012 05:44, schrieb Ralf Corsepius:
> On 07/31/2012 07:41 PM, Gedare Bloom wrote:
>> I would like to request that we freeze all commits to RTEMS and
>> consider what to do about including generated files in the repository.
>> Agreement (much less consensus) was not reached and now we have a
>> large number of automatically generated files in rtems.git that
>> substantially bloats the size of the repository.
> The sizes of the repos hardly has any impact on using the repos.
At least the transfer sizes for "git clone" should be affected. If the
generated files make up a visible amount of the total file sizes, and
these files will be regenerated very often, this will generate a lot of
versions for each of these files, and each version will be cloned for
each developer. This would not be a problem if their content stayed
stable, but obviously it ain't.
>> So far I have not seen very clear explanation why adding these
>> generated files to the git repository is the best solution long-term
>> for RTEMS.
> I already tried to explain this before.
> The advantages are:
> - No need for "bootstrap".
> - Makes bugs in configuration files more visible.
> - Makes user mistakes in configuration files more visible.
Can you elaborate the last two points further? I don't see the point
(maybe due to my limited understanding of auto*)
>> All developers should feel free to contribute to this discussion and
>> weigh-in with suggestions about what should be done.
> With all due respect, I do not see much sense in this. To me this
> discussion already has become a shit storm, because some
> semi-knowledgiable folks are spreading FUD.
You are quite fast with this view. The upcoming discussion shows, that
not all (meaning: almost no) developers are happy with this change or
are convinced with the rational of it. "semi-knowledgable" may hit the
point (at least for me), but this is also an indication, that this
change has not been preceeded by a convincing discussion. IMHO changes
with this impact on the whole source handling should have been postponed
(or published on a test branch) until a consensus has been reached.
> rtems-devel mailing list
> rtems-devel at rtems.org
embedded brains GmbH
Obere Lagerstrasse 30
email: Thomas.Doerfler at embedded-brains.de
PGP: Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel