<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">When working with GitHub, it is common to use the `origin` remote to correspond to your fork of the project. It's idiomatic to use `upstream` to refer to the upstream project. So when you said you pushed up "both revisions" I assume you meant that you pushed one or both branches to your fork, via `origin`. If your `origin` points to the upstream repository, I would expect a "push" to fail unless you have the appropriate permissions to create a new branch on the upstream repository. Since I don't see a `lists` or `assert` branch on the upstream LLVM repository, I would conclude that this must be the case.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">To answer your question: Git keeps a copy of the branch pointers for every remote that you fetch from or push to (in Git, a "pull" is a "fetch" followed by a "merge"). So when you see `origin/xxx` in your log, that refers to the commit that branch `xxx` on `origin` was pointing to when you last fetched from or pushed to it. If you had pushed anything anywhere, I would expect there to be a branch name in the commit log corresponding to the remote branch (`origin/xxx`) as well as the local one (`xxx`).</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 8, 2021 at 1:05 PM Paul C. Anagnostopoulos <<a href="mailto:paul@windfall-software.com">paul@windfall-software.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div lang="x-unicode">
<p><font face="Helvetica, Arial, sans-serif">I'm sorry, I don't
understand your first paragraph. When I ask for a list of
commits at GitHub, I see what I've included below. I'm also
confused by 'origin/lists'. Why would there be a 'lists'
branch on origin? <br>
</font></p>
<blockquote>
<p><a href="https://github.com/llvm/llvm-project/commit/6fccfd7cbdca0c1184cdb77f92329534ffde544c" target="_blank">.
. .</a></p>
<p><a href="https://github.com/llvm/llvm-project/commit/6fccfd7cbdca0c1184cdb77f92329534ffde544c" target="_blank">[InstCombine]
add icmp with no-wrap add tests; NFC</a> <span> </span> </p>
<div>
<div> <a href="https://github.com/llvm/llvm-project/commits?author=rotateright" title="View all commits
by rotateright" target="_blank">rotateright</a> committed 5 hours ago </div>
<div>
<u></u>
<u></u>
<u></u><u></u> <u></u>
<u></u>
</div>
</div>
<div>
<div>
<div>
<u></u> <u></u>
</div>
</div>
</div>
<div>
<div> </div>
</div>
<div> </div>
<div>
<p> <a href="https://github.com/llvm/llvm-project/commit/14580ce2fdd1898d130b20d9eb21bc4281868e7c" target="_blank">[TableGen]
Make behavior of list slice suffix consistent across all
v…</a> <span> </span></p>
</div>
<div>
<div> <span>Paul C. Anagnostopoulos</span>
committed 5 hours ago </div>
<div>
<u></u>
<u></u>
<u></u><u></u> <u></u>
<u></u>
</div>
</div>
<div>
<div>
<div>
<u></u>
<u></u>
</div>
</div>
</div>
<div>
<div> </div>
</div>
<div> </div>
<div>
<p> <a href="https://github.com/llvm/llvm-project/commit/3b9a15d910a8c748b1444333a4a3905a996528bc" target="_blank">[TableGen]
Add support for the 'assert' statement in multiclasses</a>
</p>
<div>
<div> <span>Paul C.
Anagnostopoulos</span> committed 5 hours ago </div>
<div>
<u></u>
<u></u>
<u></u><u></u> <u></u>
<u></u>
</div>
</div>
</div>
<div>
<div>
<div>
<u></u>
<u></u>
</div>
</div>
</div>
<div>
<div> </div>
</div>
<div> </div>
<div>
<p> <a href="https://github.com/llvm/llvm-project/commit/1206313f82f819381055dc730294ef50b3af63c9" target="_blank">[CodeGen][AArch64]
Fix isel crash for truncating FP stores</a> <span> </span></p>
</div>
<div>
<div> <a href="https://github.com/llvm/llvm-project/commits?author=david-arm" title="View all commits
by david-arm" target="_blank">david-arm</a> committed 5 hours ago </div>
<div>
<u></u>
<u></u>
<u></u><u></u> <u></u>
<u></u>
</div>
</div>
</blockquote>
<div>On 4/8/2021 1:25 PM, David Lloyd
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="font-family:arial,helvetica,sans-serif">According to
that log, neither `lists` nor `assert` appear on your GitHub
instance with those commit IDs (if you had successfully
pushed `lists`, you should expect `lists` to have the same
commit ID as `origin/lists`, which does not appear in your
log at all).</div>
<div style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif">And it's
worth noting that amending a commit does not change the
commit date, unless you explicitly tell it to do so. You
can see the separate authorship and commit dates using `git
log --pretty=fuller`. But what you see in annotations is
probably the authorship date.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Apr 8, 2021 at 12:10
PM Paul C. Anagnostopoulos <<a href="mailto:paul@windfall-software.com" target="_blank">paul@windfall-software.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>But two things are confusing. I only pushed the 'lists'
branch, not the 'assert' branch, yet both revisions are
up on GitHub. I suppose I should be careful and say that
if I pushed 'assert', I don't know how I did it.</p>
<p>Also, if you check the dates on the changed lines in
the various files, they are dated April 5 for 'lists'
and April 1 for 'assert'. But I amended the commit on
the 'lists' branch today and then pushed it.<br>
</p>
<div>On 4/8/2021 1:00 PM, David Lloyd wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="font-family:arial,helvetica,sans-serif">Branches
are just a pointer to a commit ID. This just means
that your local `main`, `lists`, and `assert`
branches all point to the same commit ID, which is
OK. Pushing one does not push the others. When you
push a branch e.g. `lists` via `git push origin
lists`, what you are doing is telling the remote
server "create or change the branch (pointer) on
your end called `lists` to refer to the same commit
ID as my local branch `lists`". It also pushes the
commits to the server (but this is strictly additive
- nothing is lost by this action). No other remote
branches would be affected by this action.</div>
<div style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif">It's
also possible to push a local branch to a remote
branch with a different name; e.g. `git push origin
foo:bar` makes a branch called `bar` on the remote
side with the same commit ID as the branch called
`foo` on the local side.</div>
<div style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif">Overall
I don't think you've broken anything, it's just that
the log output is not completely intuitive. It's
just listing all the branch names that it knows of
which happen to point to the corresponding commit ID
in the log.</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">- DML • he/him<br></div></div></div>