From: Erwin Villejo <erwinvillejo@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git pull bug report
Date: Mon, 15 Nov 2021 16:39:26 +0700 [thread overview]
Message-ID: <CADL96rtX_uw6fJEVq2u9bkPNhYXwaGT13F+cMiGgZrHQr5TP7A@mail.gmail.com> (raw)
In-Reply-To: <CADL96rs0M15E+CnycBsDqGbiibDFx4KeMthLspQH1=Bw3PS3gg@mail.gmail.com>
$ git log main github/main --graph --decorate -n 3
* commit b73d3e132f9638afbf5b98b0c278ed6b93a3ae50 (HEAD -> main)
| Author: Erwin Villejo <erwin.villejo@gmail.com>
| Date: Mon Nov 15 15:22:53 2021 +0700
|
| init activity api
|
* commit d370bf256a756a777c14609c8ad4184aa7e9e60f (github/main)
| Author: Erwin Villejo <erwin.villejo@gmail.com>
| Date: Sat Nov 13 19:18:45 2021 +0700
|
| refactor partitioning migration
|
* commit 5124511d287f1a6c384ff9766fdcc0e3e07043e8
| Author: Erwin Villejo <erwin.villejo@gmail.com>
| Date: Mon Nov 8 17:24:19 2021 +0700
|
| wip pg
$ git remote -v
github git@github.com:erwinv/database-sandbox.git (fetch)
github git@github.com:erwinv/database-sandbox.git (push)
Link to the [upstream branch on
GitHub](https://github.com/erwinv/database-sandbox/commits/main) so
you could see for yourself that my local is ahead of upstream and that
the upstream has no commits ahead of local.
Best regards,
Erwin
On Mon, Nov 15, 2021 at 4:19 PM Erwin Villejo <erwinvillejo@gmail.com> wrote:
>
> > the remote mainline have three commits ahead
> Where did you get this info? This is not true in my case.
>
> * local is ahead of upstream. confirmed by `git status`:
>
> ```
> $ git status
> On branch main
> Your branch is ahead of 'github/main' by 1 commit.
> (use "git push" to publish your local commits)
> ```
>
> If remote was ahead, `git status` would say so. And this is my
> personal repo in GitHub with only me as the sole developer/contributor
> so I can assure you that the upstream has no commits ahead of my
> local.
>
> Best regards,
> Erwin
>
> On Mon, Nov 15, 2021 at 4:12 PM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> >
> > On 15/11/21 15.56, Erwin Villejo wrote:
> > > There is nothing to reconcile since the branches have not diverged:
> > > local is ahead of upstream. So I think it is a bug, no?
> >
> > You have the situation like:
> >
> > ---o---a (your mainline)
> > \
> > b---c---d (remote mainline)
> >
> > Your mainline only have one commit ahead of base point `o`, while the remote
> > mainline have three commits ahead of `o` but unrelated. In this sense, your and
> > remote mainline is divergent - you need to either merge or rebase.
> >
> > Next time, keep your mainline pristine (don't commit any local changes on it,
> > instead branch to the topic branch and commit there).
> >
> > --
> > An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-11-15 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 8:42 git pull bug report Erwin Villejo
2021-11-15 8:54 ` Bagas Sanjaya
2021-11-15 8:56 ` Erwin Villejo
2021-11-15 9:12 ` Bagas Sanjaya
2021-11-15 9:19 ` Erwin Villejo
2021-11-15 9:39 ` Erwin Villejo [this message]
2021-11-15 18:15 ` Bryan Turner
2021-11-15 18:22 ` Erwin Villejo
2021-11-15 17:56 ` Bryan Turner
2021-11-15 20:40 ` Junio C Hamano
[not found] ` <CADL96rsnUCXchnrTa1rZ7WgJz2kDA-3TzeOiCy4AXNFdXtTmng@mail.gmail.com>
2021-11-16 1:43 ` Erwin Villejo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADL96rtX_uw6fJEVq2u9bkPNhYXwaGT13F+cMiGgZrHQr5TP7A@mail.gmail.com \
--to=erwinvillejo@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).