You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Richard gave me lots of older releases, down to development versions of TeXShop 1.0. These should be integrated into the repository.
For these, the recognition of release dates is not always completely accurate. It might be best to create master control file, which matches source file names to release dates.
Another complication is that the history in reality isn't completely linear: after version 2.x was forked off, version 1.x was maintained for some more time. Similarly, version 3.x was forked from 3.x and both were maintained in parallel for a time.
So I guess the script should do this: first import all 1.x versions in the right order, with right dates.
Then import all 2.x versions, basing the imports on the correct 1.x version at which the fork happened (which is ???? )
Then do the same for 3.x
The text was updated successfully, but these errors were encountered:
Richard gave me lots of older releases, down to development versions of TeXShop 1.0. These should be integrated into the repository.
For these, the recognition of release dates is not always completely accurate. It might be best to create master control file, which matches source file names to release dates.
Another complication is that the history in reality isn't completely linear: after version 2.x was forked off, version 1.x was maintained for some more time. Similarly, version 3.x was forked from 3.x and both were maintained in parallel for a time.
So I guess the script should do this: first import all 1.x versions in the right order, with right dates.
Then import all 2.x versions, basing the imports on the correct 1.x version at which the fork happened (which is ???? )
Then do the same for 3.x
The text was updated successfully, but these errors were encountered: