[git-users] Highlevel (but simple to implement) commands provided by default for git

Hello all, One of the things I note about git is that is provides mostly low-level and strictly necessary commands. Many highlevel commands are then implemented as alias by users, after a deep search on the internet. Adding highlevel commands, even though it could be implemented by a simple al

Re: [git-users] Highlevel (but simple to implement) commands provided by default for git

On Wed, 29 May 2013 04:23:16 -0700 (PDT) Bráulio Bhavamitra wrote: [...] > I have, as many other users, an enormous .gitconfig. I paste here > some highlevel commands of it, according to my judgement. > Mercurial provides many of these highlevel commands. [...] If your intent was to discuss if s

Re: [git-users] Highlevel (but simple to implement) commands provided by default for git

> From: Bráulio Bhavamitra > > Adding highlevel commands, even though it could be implemented by a > simple alias, would put git in another level of user experience and > create a new standard for newbie users. What git developers think > about this? It's a great idea, but beware that doing suc

Re: [git-users] Highlevel (but simple to implement) commands provided by default for git

Another aspect to consider is that Mercurial solves a lot of the user interface issues surrounding Git, while still providing much of the same functionality. I think adding a simpler interface to Git would actually destroy a lot of what sets it apart from other DVCS. I'm a fan of the Unix philosop

Re: [git-users] Highlevel (but simple to implement) commands provided by default for git

On Wed, May 29, 2013 at 8:23 AM, Bráulio Bhavamitra wrote: > Hello all, > > One of the things I note about git is that is provides mostly low-level > and strictly necessary commands. > Many highlevel commands are then implemented as alias by users, after a > deep search on the internet. > > Adding

[git-users] syncing all branches from github upstream to a fork

When you do a github fork, you get a copy of all branches in the src repo as of the moment of fork, and then they never get updated unless you do it manually, and you never get any new branches. I've been looking at ways to do this. The best I've found so far is: #!/bin/sh # usage: git-sync-upstr

[git-users] Git clone out of memory on Windows

Hi, I am unable to clone my repository. I get a message of out of memory. The server is located on Hyper-V running on Win Server 2008 R2 SP-1 The OS is Windows 7 64BIT. What do you suggest I should do? Thanks -- You received this message because you are subscribed to the Google