Am 10.11.2015 um 23:49 schrieb Stefan Beller:
On Tue, Nov 10, 2015 at 1:57 PM, Jens Lehmann wrote:
Am 10.11.2015 um 19:12 schrieb Stefan Beller:
On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton
For example, I wanted to setup "git clone" to automatically act as "git
clone --recursive". Sure I
On Wed, Nov 11, 2015 at 1:28 AM, Jeremy Morton wrote:
> On 11/11/2015 04:48, Sitaram Chamarty wrote:
>>
>> A lot of things in Unix do follow that "give you rope to hang yourself"
>> philosophy. I used to (and to *some* extent still do) think like that,
>> but some years of supporting normal users
On 11/11/15 15:42, Jeremy Morton wrote:
> On 11/11/2015 09:51, Sitaram Chamarty wrote:
>> I can only repeat what I said before: it's not all black and white.
>>
>> Reducing the opportunity to make mistakes is useful for everyone, even
>> expetrs. Especially stuff that you may have setup aeons ago
On 11/11/2015 09:51, Sitaram Chamarty wrote:
I can only repeat what I said before: it's not all black and white.
Reducing the opportunity to make mistakes is useful for everyone, even
expetrs. Especially stuff that you may have setup aeons ago and hits
you only aeons later when something (suppo
On 11/11/15 14:58, Jeremy Morton wrote:
> On 11/11/2015 04:48, Sitaram Chamarty wrote:
>> A lot of things in Unix do follow that "give you rope to hang yourself"
>> philosophy. I used to (and to *some* extent still do) think like that,
>> but some years of supporting normal users trying to do stuf
On 11/11/2015 04:48, Sitaram Chamarty wrote:
A lot of things in Unix do follow that "give you rope to hang yourself"
philosophy. I used to (and to *some* extent still do) think like that,
but some years of supporting normal users trying to do stuff has taught
me it's not always that simple.
I c
On 11/11/15 01:34, Jeremy Morton wrote:
> On 10/11/2015 18:12, Stefan Beller wrote:
>> On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton wrote:
>>> It's recently come to my attention that the "git alias" config functionality
>>> ignores all aliases that would override existing Git commands. This see
On Tue, Nov 10, 2015 at 1:57 PM, Jens Lehmann wrote:
> Am 10.11.2015 um 19:12 schrieb Stefan Beller:
>>
>> On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton
>> wrote:
>>>
>>> It's recently come to my attention that the "git alias" config
>>> functionality
>>> ignores all aliases that would override
Am 10.11.2015 um 19:12 schrieb Stefan Beller:
On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton wrote:
It's recently come to my attention that the "git alias" config functionality
ignores all aliases that would override existing Git commands. This seems
like a bad idea to me.
This ensures that
On Tue, Nov 10, 2015 at 12:04 PM, Jeremy Morton wrote:
> On 10/11/2015 18:12, Stefan Beller wrote:
>>
>> On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton
>> wrote:
>>>
>>> It's recently come to my attention that the "git alias" config
>>> functionality
>>> ignores all aliases that would override exi
On 10/11/2015 18:12, Stefan Beller wrote:
On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton wrote:
It's recently come to my attention that the "git alias" config functionality
ignores all aliases that would override existing Git commands. This seems
like a bad idea to me.
This ensures that the
On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton wrote:
> It's recently come to my attention that the "git alias" config functionality
> ignores all aliases that would override existing Git commands. This seems
> like a bad idea to me.
This ensures that the plumbing commands always work as expecte
It's recently come to my attention that the "git alias" config
functionality ignores all aliases that would override existing Git
commands. This seems like a bad idea to me.
For example, I wanted to setup "git clone" to automatically act as
"git clone --recursive". Sure I could do it in the
13 matches
Mail list logo
