git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
	Elijah Newren <newren@gmail.com>,
	Felipe Contreras <felipe.contreras@gmail.com>
Subject: [RFC/PATCH 0/3] pull: warning improvements part 2
Date: Tue, 15 Dec 2020 02:46:16 -0600	[thread overview]
Message-ID: <20201215084619.1631180-1-felipe.contreras@gmail.com> (raw)

This patch series goes on top of fc/pull-merge-rebase, however, I don't
know how I should communicate that clearly, so I'm sending this as RFC
to avoid any possible merging issues. It's not really an RFC, and in
reality this is not v1, but the end result of many iterations, simply
rebased on top of Junio's changes.

While updating the documentation (yet again) I noticed it didn't follow
from one paragraph to the next (not a good story). So I decided to
rewrite it adding a lot more detail.

The warning has also been changed completely taking into consideration
the imput Jeff King shared with us in 2013 from GitHub trainers.

And finally one low-hanging fruit patch.

I have many more in the queue though.


Felipe Contreras (3):
  doc: pull: explain what is a fast-forward
  pull: improve default warning
  pull: cleanup autostash check

 Documentation/git-pull.txt | 38 +++++++++++++++++++++++++++++++++-----
 builtin/pull.c             | 38 +++++++++++++++++++-------------------
 2 files changed, 52 insertions(+), 24 deletions(-)

-- 
2.29.2


             reply	other threads:[~2020-12-15  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15  8:46 Felipe Contreras [this message]
2020-12-15  8:46 ` [RFC/PATCH 1/3] doc: pull: explain what is a fast-forward Felipe Contreras
2020-12-15  8:46 ` [RFC/PATCH 2/3] pull: improve default warning Felipe Contreras
2020-12-15  8:46 ` [RFC/PATCH 3/3] pull: cleanup autostash check Felipe Contreras

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201215084619.1631180-1-felipe.contreras@gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).