From: Michael Haggerty Date: Mon, 11 May 2015 14:17:58 GMT Subject: Re: Multiple push remotes via aliases Message-ID: <5550BA16.2090304@alum.mit.edu> In-Reply-To: <20150510181703.GC225482@vauxhall.crustytoothpaste.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/10/2015 08:17 PM, brian m. carlson wrote: > I recently discovered that it was possible to specify multiple push > URLs for a remote. This is useful for me because some of my > projects live both on GitHub and on my own server, and some live > only one place or the other. > > One feature that I'm looking for, however, is the ability to > specify those URLs by reference to another remote. For example, > making the remote def (default) refer to the remotes gh and > upstream instead of duplicating the URLs. This makes dealing with > URL changes easier and goes along with the DRY approach. > > I don't think we already have this functionality (at least I don't > see code for it), and I'd like to implement it, but maybe the > documentation is just missing and I should submit a patch for that > instead. Do we have such a thing, and if not, do people think this > is a worthwhile feature? For fetching, we already have > remotes. The list of remotes which are fetched by "git > remote update ". See git-remote(1). ISTM that your feature is akin to this one and could piggyback on the same configuration. By analogy with "git remote update ", the corresponding command could be git remote push [...] You suggested being able to run something like git push [...] which is a little bit shorter. If so, then it is natural to ask whether should be allowed in place of whenever it makes sense, as a general UI principle. If so, then git fetch [...] could be shorthand for "git remote update [...]". But please note that I haven't thought about whether the -> generalization could be done consistently, vs. whether the groupwise commands are different enough from the single-repo commands that the supposed generalization would be more confusing than useful. Michael - -- Michael Haggerty mhagger@alum.mit.edu -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlVQuhUACgkQwg9mrRwfmAkFbQCghrQhBaerq0W7suJzu0cr7RGW Cy0AoIkvgbWmOnwJfeldk73vNMPbc197 =arW/ -----END PGP SIGNATURE-----