[haiku-development] Re: No tagged releases in our git repository?
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 30 Jan 2012 03:24:15 +0100
On 2012-01-29 at 19:39:37 [+0100], Matt Madia <mattmadia@xxxxxxxxx> wrote:
> On Sun, Jan 22, 2012 at 19:00, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> > Matt Madia wrote:
> >> Am I overlooking something or are the tagged releases R1a1 (r33109) ,
> >> R1a2
> >> (r36769) and R1a3 (r42211) absent in our git repositories?
> >
> > The release tags don't seem to have made it into the git repository. With
> > tagging in svn being actually a copy operation, the hrev* tags are
> > naturally missing as well. Since the release branches were closed after
> > the release and remained unchanged (save for a small hickup in r1alpha3),
> > the release versions are identical to the heads of the branches
> > (r1alpha{1,2,3}), though. We could tag them for good measure, but we
> > should agree on a naming scheme first. :-)
>
> What about 'orrev' or 'rrev' ?
> hrev = Haiku revision
> btrev = BuildTools revision
> orrev = Official Release revision
I was rather thinking of something like r1alpha{1,2,3}-final. In principle
r1alpha{1,2,3} would be perfect tag names, but since those clash with the
branch names... Alternatively the branches could be renamed, of course
(r1alpha{1,2,3}-branch).
CU, Ingo
Other related posts:
