|From:||Dr . Jürgen Sauermann|
|Subject:||Re: Moving from svn to git and source forge to github.|
|Date:||Sun, 22 Dec 2019 15:45:22 +0100|
|User-agent:||Mozilla/5.0 (X11; Linux i686; rv:60.0) Gecko/20100101 Thunderbird/60.6.1|
Ad 0. Actually there is a worse system: clearcase. Not sure if it still exists. I still recall from
about 20 years ago, after travelling across Europe to attend a code review, that I couldn't
see a single line of code, apparently due to missing "views", and nobody was able to fix
that (the responsible clearcase admin was on vacation or so).
Ad 5. I ran into exactly that problem. After to crowd moved to git, I moved my (at that time
separate) SVN repos into one git repo with one subdir per SVN repo. Reason was
dependencies between two of the repos that came up after the repose were created.
Some other repos were moved into other subdirs of that same git repo. After that, I got
millions of merge conflicts when co-workers pushed changes into their directories.
It was often weeks during which I could not push my changes, and in the end I had to
submitted my changes by email. In svn you can simply delete conflicting dirs and
svn up will happily recreate them. In git this will send you into a merge because the
delete is another change that wants to be pushed (which you can't due to still
Ad 6. You cannot commit empty directories in git. How stupid is that? I know there are
workarounds to fix this, but why would you? I normally start a new project with empty
directories: trunk, tags, and branches. Push them in git and nothing happens. At that
point your local build may succeed while a fresh check-out of the same repo will fail.
On 12/22/19 12:34 PM, Blake McBride wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|