From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 6F7DE1F66F for ; Thu, 12 Nov 2020 20:48:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727168AbgKLUsE (ORCPT ); Thu, 12 Nov 2020 15:48:04 -0500 Received: from cloud.peff.net ([104.130.231.41]:56394 "EHLO cloud.peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727150AbgKLUsD (ORCPT ); Thu, 12 Nov 2020 15:48:03 -0500 Received: (qmail 22110 invoked by uid 109); 12 Nov 2020 20:48:03 -0000 Received: from Unknown (HELO peff.net) (10.0.1.2) by cloud.peff.net (qpsmtpd/0.94) with ESMTP; Thu, 12 Nov 2020 20:48:03 +0000 Authentication-Results: cloud.peff.net; auth=none Received: (qmail 1499 invoked by uid 111); 12 Nov 2020 20:48:02 -0000 Received: from coredump.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.2) by peff.net (qpsmtpd/0.94) with (TLS_AES_256_GCM_SHA384 encrypted) ESMTPS; Thu, 12 Nov 2020 15:48:02 -0500 Authentication-Results: peff.net; auth=none Date: Thu, 12 Nov 2020 15:48:02 -0500 From: Jeff King To: Chris Torek Cc: =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason , Git List , Junio C Hamano , Johannes Schindelin , Stefan Beller Subject: Re: How do I "git fetch" with a custom but a default remote? Message-ID: <20201112204802.GA707750@coredump.intra.peff.net> References: <20201111151754.31527-1-avarab@gmail.com> <877dqqhd3s.fsf@evledraar.gmail.com> <20201112185146.GD701197@coredump.intra.peff.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Thu, Nov 12, 2020 at 11:26:25AM -0800, Chris Torek wrote: > On Thu, Nov 12, 2020 at 10:52 AM Jeff King wrote: > > If we were starting from scratch, then I think that might have been > > nicer, because --default-remote would be implied if there is no > > "--remote" option. And then my lazy-to-type: > > > > git fetch topic > > > > would just work. But given that we have the positional > > parameter already, I don't think adding --remote gives much value. And > > it raises the question of what "git fetch --remote=foo --remote=bar" > > means (I think the answer is last-one-wins). > > Since `git fetch` can fetch from more than one remote, it seems to me > to make more sense to mean "fetch from each". Ah, right, I forgot that --multiple existed. Without it, specifying multiple remotes makes no sense at all. But perhaps giving multiple --remote would implicitly specify "--multiple". That makes sense to me. > (This isn't necessarily an argument in favor of adding these options, > just my suggestion for what multiple `--remote=` settings would mean.) Likewise. "makes sense" above mostly means I would not object to it, but I am not advocating for it. :) -Peff