Re: Allowing override of the default "origin" nickname
- From
Mark Levedahl <mlevedahl@gmail.com>
- Date
- Jan 11, 2008, 16:39 UTC
- Message-ID
- <30e4a070801110839j6b27e224j9a83fc9975f2e4c6@mail.gmail.com>
- In-Reply-To
- <alpine.LSU.1.00.0801111501510.31053@racer.site>
On Jan 11, 2008 10:03 AM, Johannes Schindelin >
Show 5 quoted lines
> Okay, so with your change the user has to either remember or lookup which > is the default remote. Without your change, the user has to either > remember or lookup where origin points to. > > I still think your change does not help.
That's a theoretical argument: my *experience* with trying to make the current workflow operate was sufficiently bad and troublesome that it caused me to write code and fix it to enable the new workflow. Also, absent submodules the new workflow is fully supported by branch.<name>.remote: are you advocating the elimination of that existing feature?
Mark