git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Subject: Blog post: git update: the odyssey for a sensible git pull
Date: Mon, 05 Jul 2021 10:28:23 -0500	[thread overview]
Message-ID: <60e325175e689_1baed32081c@natae.notmuch> (raw)

Hello,

As I mentioned in my `git update` patch series [1], I spent several days
re-reading old threads looking for anything related to `git pull` and
fast-forward throughout the entire history of the git mailing list.

I documented everything that I found of interest, and the result is a
pretty lengthy article.

Long story short: a new `git update` command fixes all the issues people
have been reporting for almost a decade now.

Even if it's not a particularly interesting read, it's a good reference
that records all the attempts that have been made, along with many ideas
and proposals.

https://felipec.wordpress.com/2021/07/05/git-update/

[1] https://lore.kernel.org/git/20210705123209.1808663-1-felipe.contreras@gmail.com/

-- 
Felipe Contreras

                 reply	other threads:[~2021-07-05 15:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=60e325175e689_1baed32081c@natae.notmuch \
    --to=felipe.contreras@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).