From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: Useful tracking branches and auto merging
Date: Tue, 5 Oct 2010 20:49:25 +0300 [thread overview]
Message-ID: <AANLkTinXJ5E_U=5uP_zvWLQBssQsYC74JyVv1N3-eMXK@mail.gmail.com> (raw)
In-Reply-To: <7vk4lw7g2m.fsf@alter.siamese.dyndns.org>
On Tue, Oct 5, 2010 at 7:35 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>
>> Maybe 'git pull --all' could be taught to eventually do this? That
>> would be incompatible with its current behavior of fetching everything
>> and merging some random branch, but I don't think anyone is relying
>> on that.
>
> I vaguely recall that we had discussions to disable "git pull --all",
> which most likely is a mistake?
I believe this use-case is valid:
* The user wants *all* his remote tracking branches to point to the
latest branch head in all the repos in the case the can be
fast-forwarded, and in the case they can't, print an error and
continue with the rest.
Right now I would have to do 'git fetch --all' go to every remote
tracking branch, and do 'git merge @{upstream}'.
Do you have a better idea how to achieve that instead of 'git pull --all'?
--
Felipe Contreras
next prev parent reply other threads:[~2010-10-05 17:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 20:44 Useful tracking branches and auto merging Felipe Contreras
2010-10-04 20:46 ` Jonathan Nieder
2010-10-04 20:56 ` Felipe Contreras
2010-10-04 20:57 ` Jonathan Nieder
2010-10-04 21:06 ` Felipe Contreras
2010-10-10 17:15 ` Clemens Buchacher
2010-10-10 17:30 ` Felipe Contreras
2010-10-10 17:45 ` Clemens Buchacher
2010-10-10 17:48 ` Felipe Contreras
2010-10-05 16:35 ` Junio C Hamano
2010-10-05 17:49 ` Felipe Contreras [this message]
2010-10-05 20:10 ` Junio C Hamano
2010-10-07 10:04 ` 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='AANLkTinXJ5E_U=5uP_zvWLQBssQsYC74JyVv1N3-eMXK@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
/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).