Magnus Hagander wrote:
> Heikki Linnakangas wrote:
>> Another problem with git-cvsimport is that only branches that have had
>> any commits to them show up in the GIT repository. This hack won't fix
>> that. If cvsps injected a dummy "branch commit" at the right place,
>> instead of the reordering that my hack does, that might be fixed too.
>
> Do we *have* any branches that have had no commits?
No, but we will as soon as we branch again.
> And in this case, do
> we *care* that they don't show up? I assume they will show up as soon as
> we get the first commit?
I guess we could live with them not showing up until first commit.
>> What are we going to do about this? I have the feeling that I have the
>> greatest itch to get the repository fixed. I propose that I will try
>> that dummy "branch commit" hack in cvsps, and if it works out, create a
>> new GIT repository using that. That would replace the current
>> repository, which means that people working against that repository will
>> need to use "git-fetch --force" to update their clones, and rebase their
>> own branches. It would also be good to contribute the hack into upstream
>> cvsps (whatever fork is considered upstream).
>
> Sounds like a reasonable plan to me. We should be careful to test out
> all parts before we do it, though, so users don't have to rebase more
> than once!
Yep. Need to test what happens when new branches are created, at least.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
