Segher Boessenkool <seg...@kernel.crashing.org>:
> Or doing what everyone else does: put an empty .gitignore file in
> otherwise empty directories.
That is an ugly kludge that I will have no part of whatsoever.
Conversion artifacts like this are sources of cognitive friction and
confusion that take developers' attention away from the substantive
part of their work. Each individual one may be minor, but the
cumulative effect can be a chronic distraction that us not less
because developers are unware or ibly half-aware of it.
Thus, the goal of a repository converter should be to bridge smoothly
between the native idioms of the source and target systems,
*minimizing* conversion artifacts.
The ideal should be to produce a converted history that looks as much
as possible like it has always been under the target
system. Developers should have no need to know or care that the
history used to be managed differently unless they need to do
sonething that *unavoidably* crosses that boundary, like looking uo a
legacy ID grom an old bug report.
Reposurgeon was designed for this goal from the beginning.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
