Skip to content

Handling of merges that contained empty directories #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
baudren opened this issue May 24, 2018 · 3 comments
Open

Handling of merges that contained empty directories #47

baudren opened this issue May 24, 2018 · 3 comments
Labels

Comments

@baudren
Copy link

baudren commented May 24, 2018

Hello,

we have the following situation:

  • a commit on an SVN branch introduced two empty directories.
  • this branch is later merged on the trunk

Applying the svn2git tool with the option --empty-dirs, the commit on the SVN branch added, as expected, two .gitignore files.

However, the subsequent merge commits did not carry this information, and I sort-of see the point: only the content of the SVN merge commit got transcribed and reproduced, but it creates this weird situation where the master (ex trunk) does not contain exactly the same content at the other branch, despite having done a merge.

Would there be any work-around on this? The easy solution is to reperform the merge, at the end of the migration, where this time the empty .gitignore will be picked, but if there would be a cleaner way, that would be nice.

Thanks in advance, and thank you for the tool!

@tnyblom
Copy link
Contributor

tnyblom commented May 24, 2018

Hi,

Thanks for the report, but this project is not really maintained any longer so unless someone provides a patch the chance of a fix is unfortunately quite low.

/Cheers
Torgny

@itineric
Copy link

Hi,

Had the same issue during my migration, fixed it. See PR #78 .
Fix works in my case, hope it works in yours too.

Eric

@Vampire
Copy link
Contributor

Vampire commented Jul 12, 2020

can this be closed then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants