From: Damien Robert <damien.olivier.robert+gmane@gmail.com>
To: git@vger.kernel.org
Subject: Re: Summary of the problems with git pull
Date: Tue, 6 May 2014 20:03:15 +0000 (UTC) [thread overview]
Message-ID: <lkbf63$p8l$1@ger.gmane.org> (raw)
In-Reply-To: 5366db742d494_18f9e4b308aa@nysa.notmuch
Felipe Contreras wrote in message
<5366db742d494_18f9e4b308aa@nysa.notmuch>:
> == git update ==
>
> Another proposed solution is to have a new command: `git update`. This
> command would be similar to `git pull --ff-only` by default, but it
> could be configured to do merges instead, and when doing so in reverse.
Thanks for the nice summary.
As a user, I am very much in favor of adding a `git update` command. In
fact I already have a ruby script that does such a thing (fast-forward all my
local branches that have an upstream configured), so it would be nice to
have it directly in git core.
next prev parent reply other threads:[~2014-05-06 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 0:29 Summary of the problems with git pull Felipe Contreras
2014-05-06 20:03 ` Damien Robert [this message]
2014-05-07 10:39 ` Ping Yin
2014-05-10 8:53 ` Felipe Contreras
2014-05-28 7:13 ` Philippe Vaucher
2014-05-28 8:39 ` Felipe Contreras
-- strict thread matches above, loose matches on Subject: below --
2014-05-06 10:58 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lkbf63$p8l$1@ger.gmane.org' \
--to=damien.olivier.robert+gmane@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.