[Biopython-dev] history on github - where are the tags?

[Peter]

On Sun, Apr 26, 2009 at 1:08 PM, Bartek Wilczynski
<bartek at rezolwenta.eu.org> wrote:
> Hi all,
>
> On Wed, Apr 22, 2009 at 11:23 AM, Peter <biopython at maubp.freeserve.co.uk> wrote:
>>
>> If you can fix the current git hub repository, great.
>>
> I 've finally found some time to fix the tag issue in our repository.
> I've actually spent some time looking at git-rebase (learned a lot,
> but nothing useful for our problem. Then I realised that since tags
> are just references to commits, we need to move them to the trunk
> (instead of re-basing the trunk).
>
> Long story short - assuming you are in the directory of your git repo
> you can fix any particular tag wit a single command. E.g. If you want
> to fix the biopython-149 tag, you do:
> git tag -f biopython-149 biopython-149~1
>
> -f option enforces the replacement of the existing label, while
> biopython-149~1 references the parent commit of our empty tag commit
> (you can also use ~2 for a grand parent and so on).
>
> You can see the effect of this procedure (as seen in gitx -- a very
> nice tool) in the attached images.
>
> If you want to fix all biopython tags, you simply do:
>
> for t in `git tag|grep biopython`; do git tag -f $t $t~1; done
>
> It  works locally, the changes can be pushed back to github (need
> --tags -f to force tag renames),
> I've done this on my branch of biopython on github.
>
> If there are no objections to the way tags are handled, I can try to
> update the trunk.
> This is a bit tricky, because I need to make the update scripts work
> nicely with moving
> the tags, but it should be doable.

I say give this a go - fingers crossed :)

>> The old conversion's deletion is still in progress, it must have stalled:
>> http://support.github.com/discussions/repos/485-reposiotry-stuck-in-rename
>
> Seems to be gone now. that's one problem less :)

Great.  I did have reminded them, but they solved it.

>>
>> If we can fix the tags, great.  If we can also remap the authors to
>> their git usernames, even better.
>>
> This is doable in the current setup. I don't know whether we need to
> do this. The old commits
> are signed by the same credentials (name, e-mail) as on CVS server. If
> we start re-mapping them
> now, we are going to have essentially a new commit history, so
> everybody would need to rebase their
> branches... I don't see a problem of having old commits signed with
> old e-mails, and new commits
> signed by new. Especially, that everybody can have multiple e-mails
> assigned to their github account
> (that's how I did with mine).

That would be simpler.  I'll have to try on my github account...

Peter