Duncan P. N. Exon Smith via llvm-dev
2016-Feb-05 23:25 UTC
[llvm-dev] Why do we have a git tag called "release_35@215010"?
> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to.``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested URL returned error: 403 ``` Who has access to this?> Doesn't really seem like it matters though.Not important, surely, but we might as well clean it up!> > On Fri, Feb 5, 2016 at 5:34 PM, Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I.e., I see this when I run `git fetch`: > ``` > $ git fetch -v llvm.org > From http://llvm.org/git/llvm > = [up to date] master -> llvm.org/master > = [up to date] release_1 -> llvm.org/release_1 > = [up to date] release_16 -> llvm.org/release_16 > = [up to date] release_20 -> llvm.org/release_20 > = [up to date] release_21 -> llvm.org/release_21 > = [up to date] release_22 -> llvm.org/release_22 > = [up to date] release_23 -> llvm.org/release_23 > = [up to date] release_24 -> llvm.org/release_24 > = [up to date] release_25 -> llvm.org/release_25 > = [up to date] release_26 -> llvm.org/release_26 > = [up to date] release_27 -> llvm.org/release_27 > = [up to date] release_28 -> llvm.org/release_28 > = [up to date] release_29 -> llvm.org/release_29 > = [up to date] release_30 -> llvm.org/release_30 > = [up to date] release_31 -> llvm.org/release_31 > = [up to date] release_32 -> llvm.org/release_32 > = [up to date] release_33 -> llvm.org/release_33 > = [up to date] release_34 -> llvm.org/release_34 > = [up to date] release_35 -> llvm.org/release_35 > = [up to date] release_35 at 215010 -> llvm.org/release_35 at 215010 > = [up to date] release_36 -> llvm.org/release_36 > = [up to date] release_37 -> llvm.org/release_37 > = [up to date] release_38 -> llvm.org/release_38 > = [up to date] stable -> llvm.org/stable > = [up to date] testing -> llvm.org/testing > ``` > The release_35 at 215010 looks bogus. Why is it there? If there's no good reason, who has permission to remove it? > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >
Anton Korobeynikov via llvm-dev
2016-Feb-05 23:30 UTC
[llvm-dev] Why do we have a git tag called "release_35@215010"?
git mirror is read-only. On Sat, Feb 6, 2016 at 2:25 AM, Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote:> >> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: >> >> That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. >> It can be deleted now, if anyone wants to. > > ``` > $ git push llvm.org :release_35 at 215010 > fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested URL returned error: 403 > ``` > > Who has access to this? > >> Doesn't really seem like it matters though. > > Not important, surely, but we might as well clean it up! > >> >> On Fri, Feb 5, 2016 at 5:34 PM, Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> I.e., I see this when I run `git fetch`: >> ``` >> $ git fetch -v llvm.org >> From http://llvm.org/git/llvm >> = [up to date] master -> llvm.org/master >> = [up to date] release_1 -> llvm.org/release_1 >> = [up to date] release_16 -> llvm.org/release_16 >> = [up to date] release_20 -> llvm.org/release_20 >> = [up to date] release_21 -> llvm.org/release_21 >> = [up to date] release_22 -> llvm.org/release_22 >> = [up to date] release_23 -> llvm.org/release_23 >> = [up to date] release_24 -> llvm.org/release_24 >> = [up to date] release_25 -> llvm.org/release_25 >> = [up to date] release_26 -> llvm.org/release_26 >> = [up to date] release_27 -> llvm.org/release_27 >> = [up to date] release_28 -> llvm.org/release_28 >> = [up to date] release_29 -> llvm.org/release_29 >> = [up to date] release_30 -> llvm.org/release_30 >> = [up to date] release_31 -> llvm.org/release_31 >> = [up to date] release_32 -> llvm.org/release_32 >> = [up to date] release_33 -> llvm.org/release_33 >> = [up to date] release_34 -> llvm.org/release_34 >> = [up to date] release_35 -> llvm.org/release_35 >> = [up to date] release_35 at 215010 -> llvm.org/release_35 at 215010 >> = [up to date] release_36 -> llvm.org/release_36 >> = [up to date] release_37 -> llvm.org/release_37 >> = [up to date] release_38 -> llvm.org/release_38 >> = [up to date] stable -> llvm.org/stable >> = [up to date] testing -> llvm.org/testing >> ``` >> The release_35 at 215010 looks bogus. Why is it there? If there's no good reason, who has permission to remove it? >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
Duncan P. N. Exon Smith via llvm-dev
2016-Feb-06 03:06 UTC
[llvm-dev] Why do we have a git tag called "release_35@215010"?
Right, it's read-only for me. Who has access to it?> On 2016-Feb-05, at 15:30, Anton Korobeynikov <anton at korobeynikov.info> wrote: > > git mirror is read-only. > > On Sat, Feb 6, 2016 at 2:25 AM, Duncan P. N. Exon Smith via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >>> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: >>> >>> That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. >>> It can be deleted now, if anyone wants to. >> >> ``` >> $ git push llvm.org :release_35 at 215010 >> fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested URL returned error: 403 >> ``` >> >> Who has access to this? >> >>> Doesn't really seem like it matters though. >> >> Not important, surely, but we might as well clean it up! >> >>> >>> On Fri, Feb 5, 2016 at 5:34 PM, Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> I.e., I see this when I run `git fetch`: >>> ``` >>> $ git fetch -v llvm.org >>> From http://llvm.org/git/llvm >>> = [up to date] master -> llvm.org/master >>> = [up to date] release_1 -> llvm.org/release_1 >>> = [up to date] release_16 -> llvm.org/release_16 >>> = [up to date] release_20 -> llvm.org/release_20 >>> = [up to date] release_21 -> llvm.org/release_21 >>> = [up to date] release_22 -> llvm.org/release_22 >>> = [up to date] release_23 -> llvm.org/release_23 >>> = [up to date] release_24 -> llvm.org/release_24 >>> = [up to date] release_25 -> llvm.org/release_25 >>> = [up to date] release_26 -> llvm.org/release_26 >>> = [up to date] release_27 -> llvm.org/release_27 >>> = [up to date] release_28 -> llvm.org/release_28 >>> = [up to date] release_29 -> llvm.org/release_29 >>> = [up to date] release_30 -> llvm.org/release_30 >>> = [up to date] release_31 -> llvm.org/release_31 >>> = [up to date] release_32 -> llvm.org/release_32 >>> = [up to date] release_33 -> llvm.org/release_33 >>> = [up to date] release_34 -> llvm.org/release_34 >>> = [up to date] release_35 -> llvm.org/release_35 >>> = [up to date] release_35 at 215010 -> llvm.org/release_35 at 215010 >>> = [up to date] release_36 -> llvm.org/release_36 >>> = [up to date] release_37 -> llvm.org/release_37 >>> = [up to date] release_38 -> llvm.org/release_38 >>> = [up to date] stable -> llvm.org/stable >>> = [up to date] testing -> llvm.org/testing >>> ``` >>> The release_35 at 215010 looks bogus. Why is it there? If there's no good reason, who has permission to remove it? >>> _______________________________________________ >>> LLVM Developers mailing list >>> llvm-dev at lists.llvm.org >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >>> >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Saint Petersburg State University