| Re: [tcf-dev] git tags for tcf sources |
|
Yes I am, but I don’t work with the repo on a daily basis.
It may take a while until I get to applying the tags. I had hoped that some other committers who have the repo updated anyways could do this more quickly. Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Stieber, Uwe Hi Martin, You are committer to the TCF project yourself, are you not? Best regards, Uwe
J From:
tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin Dear committers, We don’t currently have tags for the tcf source as it was at the time of our recent releases (1.0 , 1.0.1 , 1.0.2 , 1.1). Could somebody apply these in retrospect (this should be possible based on the date of commit) ? Advantage would be that the respective agent zip / tarball’s are auto-generated by git.eclipse.org like it’s the case for CDT: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/ I suggest using tags like in CDT, i.e. TCF_1_0_0 , TCF_1_0_1 , TCF_1_0_2 , TCF_1_1_0 It’s less burning for the org.eclipse.tcf repository since that is released via the downloads server, but still having the tags would be helpful such that in the commit logs any adopter can see easily what changed
after/before a release. Who could help out applying these tags to git ? Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect
– Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 |