<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <div class="moz-cite-prefix">On 2/11/2013 4:37 PM, kenji hara wrote:<br>
    </div>
    <blockquote
cite="mid:CAFDvkcugH324LeyERbEUhw28w1Mz=_HSuPQ+Y4Cme82Chqbh5g@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">2013/2/12 Leandro Lucarella <span
              dir="ltr"><<a moz-do-not-send="true"
                href="mailto:luca@llucax.com.ar" target="_blank">luca@llucax.com.ar</a>></span><br>
            <blockquote class="gmail_quote"
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Walter
              Bright, el 11 de February a las 12:21 me escribiste:<br>
              <div class="im">><br>
                > On 2/11/2013 1:59 AM, kenji hara wrote:<br>
                > ><br>
                > >--- commang example<br>
                > ># fetch all remote branches<br>
                > >git fetch upstream<br>
                ><br>
                > How is that different from "git remote update" ?<br>
                <br>
              </div>
              git fetch upstream will only fetch new stuff from the
              upstream remote<br>
              repository and will set the FETCH_HEAD reference.<br>
              <br>
              git remove update will fetch new stuff from all the remote
              repositories<br>
              without touching FETCH_HEAD.</blockquote>
            <div><br>
            </div>
            <div>Because I always control remotes origin and upstream
              separately.<br>
            </div>
            <div>You can use "git remote update" instead.</div>
            <div> </div>
            <blockquote class="gmail_quote"
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div class="im">
                > ># Forcely re-tagging<br>
                > >git tag -f v2.062-b1 upstream/staging~0<br>
                ><br>
                > What is the ~0 for?<br>
                <br>
              </div>
              It has no effect, I don't know why he used it. REF~N is
              used to specify<br>
              the Nth commit before the reference REF (for example
              HEAD~3 is 3 commits<br>
              before HEAD, and is the same as specifying HEAD^^^). So
              REF~0 is the<br>
              same as REF.</blockquote>
            <div><br>
            </div>
            <div>Yes, it is no effect, but a tag sticks always to a
              commit, not branch.</div>
            <div>The form "REF~0" definitely represents a commit object,
              even if REF refers a branch.<br>
            </div>
            I used it in order to make the command more descriptive.</div>
          <div class="gmail_quote"><br>
          </div>
          <div class="gmail_quote">Kenji Hara</div>
        </div>
      </div>
      <br>
    </blockquote>
    <br>
    Thanks, I thought the ~0 was tty noise!<br>
  </body>
</html>