On 12 May 2014 14:33, Tom Stellard <tom at stellard.net> wrote:> Are you talking about adding git tags? What is the process for doing this?SVN tags, but yeah. You can take note of the commit that we produced the last candidate, but it'd be good to tag all repos with a release number. I'm not sure how people do it, but I'd assume the tags should follow the same as it's done for the main releases. If there isn't any, we should definitely create one. Bill Wendling should be able to confirm the status. cheers, --renato
On May 12, 2014, at 6:52 AM, Renato Golin <renato.golin at linaro.org> wrote:> On 12 May 2014 14:33, Tom Stellard <tom at stellard.net> wrote: >> Are you talking about adding git tags? What is the process for doing this? > > SVN tags, but yeah. You can take note of the commit that we produced > the last candidate, but it'd be good to tag all repos with a release > number. > > I'm not sure how people do it, but I'd assume the tags should follow > the same as it's done for the main releases. If there isn't any, we > should definitely create one. > > Bill Wendling should be able to confirm the status.Normally, I get a volunteer *cough*aKor*cough* to create the git tags/branches. -bw
> Normally, I get a volunteer *cough*aKor*cough* to create the git tags/branches.Yeah. Historically, we have far more branches in SVN than we'd like to export as proper GIT branches. Hence release branch creation is pretty manual. I will create them. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
The branch should already be there, because we mirror release_34 branch. We stopped to make tags ~ 2 releases ago, because git svn created orphaned ones (mostly due to our directory layout - we do not "tag" a particular commit, instead, we're creating separate dirs, etc.). On Mon, May 12, 2014 at 5:52 PM, Renato Golin <renato.golin at linaro.org> wrote:> On 12 May 2014 14:33, Tom Stellard <tom at stellard.net> wrote: >> Are you talking about adding git tags? What is the process for doing this? > > SVN tags, but yeah. You can take note of the commit that we produced > the last candidate, but it'd be good to tag all repos with a release > number. > > I'm not sure how people do it, but I'd assume the tags should follow > the same as it's done for the main releases. If there isn't any, we > should definitely create one. > > Bill Wendling should be able to confirm the status. > > cheers, > --renato > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev-- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
On 19/05/2014 00:07, Anton Korobeynikov wrote:> The branch should already be there, because we mirror release_34 branch. > > We stopped to make tags ~ 2 releases ago, because git svn created > orphaned ones (mostly due to our directory layout - we do not "tag" a > particular commit, instead, we're creating separate dirs, etc.).Just to say, thanks for maintaining the git mirror! The extra time you've put into tagging and branching correctly instead of providing a straight git-svn dump has undoubtedly paid back in developer time many times over. Alp.> > On Mon, May 12, 2014 at 5:52 PM, Renato Golin <renato.golin at linaro.org> wrote: >> On 12 May 2014 14:33, Tom Stellard <tom at stellard.net> wrote: >>> Are you talking about adding git tags? What is the process for doing this? >> SVN tags, but yeah. You can take note of the commit that we produced >> the last candidate, but it'd be good to tag all repos with a release >> number. >> >> I'm not sure how people do it, but I'd assume the tags should follow >> the same as it's done for the main releases. If there isn't any, we >> should definitely create one. >> >> Bill Wendling should be able to confirm the status. >> >> cheers, >> --renato >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-- http://www.nuanti.com the browser experts