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

[Bartek Wilczynski]

Hi all,

Sorry for being quiet all that time, but the conference (+jet lag both
ways) proved to be more engaging than I thought.

For the tags, they were not pushed to github before, because I didn't
know I need to specifically do it qith git push --tags.

Now they are pushed to the repository and you can fetch them to local
copies by git pull -t in any local directory which resulted from
cloning the official branch.

They probably won't get automatically transfered to derived branches,
I guess you need to pull
them from the original (official) branch.

cheers
Bartek

On Wed, Mar 25, 2009 at 12:49 AM, Bartek Wilczynski <barwil at gmail.com> wrote:
> Hi all,
>
> Sorry for being quiet all that time, but the conference (+jet lag both
> ways) proved to be more engaging than I thought.
>
> For the tags, they were not pushed to github before, because I didn't
> know I need to specifically do it qith git push --tags.
>
> Now they are pushed to the repository and you can fetch them to local
> copies by git pull -t in any local directory which resulted from
> cloning the official branch.
>
> They probably won't get automatically transfered to derived branches,
> I guess you need to pull
> them from the original (official) branch.
>
> cheers
> Bartek
>
> On Tue, Mar 17, 2009 at 10:06 AM, Peter <biopython at maubp.freeserve.co.uk> wrote:
>> Hi Bartek et al,
>>
>> I've just been looking over the github mirror of CVS, and wanted to
>> see it presented the history of individual files.  For example, this
>> page looks at the Bio/SeqRecord.py history using ViewCVS:
>> http://cvs.biopython.org/cgi-bin/viewcvs/viewcvs.cgi/biopython/Bio/SeqRecord.py?cvsroot=biopython
>>
>> For comparison, in GitHub,
>> http://github.com/biopython/biopython/commits/master/Bio/SeqRecord.py
>>
>> As you can see, all the comments and changes are there - which is
>> great.  But I can't see the CVS tag information, which I assume would
>> be converting into git tags.  Is this information present in the git
>> repository, but not shown by github, or was it lost during the
>> migration?  This might seem like a little thing, but I have found it
>> incredibly important for tracing bugs reported in older releases, for
>> example in narrowing down when something changed.
>>
>> Peter
>>
>
>
>
> --
> Bartek Wilczynski
> ==================
> Postdoctoral fellow
> EMBL, Furlong group
> Meyerhoffstrasse 1,
> 69012 Heidelberg,
> Germany
> tel: +49 6221 387 8433
>



-- 
Bartek Wilczynski
==================
Postdoctoral fellow
EMBL, Furlong group
Meyerhoffstrasse 1,
69012 Heidelberg,
Germany
tel: +49 6221 387 8433