FAQ
I usually build from source, and I use the *release* tag to always keep my
releases up to date.

With the move to git, it seems the release tag was not carried over.

The workaround is to hardcode go1.4 in my script, and change it each time a
new go release is announced.



--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

  • Fazlul Shahriar at Dec 19, 2014 at 1:25 pm
    Tags are more permanent in git. See "On Re-tagging" section in git-tag(1)
    <http://git-scm.com/docs/git-tag>.

         fhs
    On Fri, Dec 19, 2014 at 4:52 AM, Ugorji wrote:

    I usually build from source, and I use the *release* tag to always keep
    my releases up to date.

    With the move to git, it seems the release tag was not carried over.

    The workaround is to hardcode go1.4 in my script, and change it each time
    a new go release is announced.



    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Ugorji at Dec 19, 2014 at 1:30 pm
    Ah. Got it. Thanks much.
    On Friday, December 19, 2014 8:25:50 AM UTC-5, Fazlul Shahriar wrote:

    Tags are more permanent in git. See "On Re-tagging" section in git-tag(1)
    <http://git-scm.com/docs/git-tag>.

    fhs

    On Fri, Dec 19, 2014 at 4:52 AM, Ugorji <ugo...@gmail.com <javascript:>>
    wrote:
    I usually build from source, and I use the *release* tag to always keep
    my releases up to date.

    With the move to git, it seems the release tag was not carried over.

    The workaround is to hardcode go1.4 in my script, and change it each time
    a new go release is announced.



    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-dev+...@googlegroups.com <javascript:>.
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-dev @
categoriesgo
postedDec 19, '14 at 9:52a
activeDec 19, '14 at 1:30p
posts3
users2
websitegolang.org

2 users in discussion

Ugorji: 2 posts Fazlul Shahriar: 1 post

People

Translate

site design / logo © 2021 Grokbase