Re: EasyGit Integration

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Jun 10, 2009, 22:04 UTC
Message-ID: <94a0d4530906101504j7928b0aaqff4c30c5136eec44@mail.gmail.com>
In-Reply-To: <d411cc4a0906091159r51e7d16t4d66c6225322fb60@mail.gmail.com>

On Tue, Jun 9, 2009 at 9:59 PM, Scott Chacon<schacon@gmail.com> wrote:

Show 17 quoted lines

> Hey all,
>
> I have been playing with the EasyGit project lately and I have been
> really impressed.  I looked back to the last announcement here and the
> conversation didn't really go anywhere, sadly.  I thought it might be
> nice to adopt or at least consider a number of the design decisions
> they made in modifying the defaults and commands available.  Perhaps
> as a 1.7 goal or something?  I like it because it addresses a lot of
> the issues that I hear from beginning users:
>
> * breaks the various things that 'checkout' does into separate
> commands - moves 'revert' to doing what 'checkout -- path' does, moves
> current 'revert' to 'cherry-pick --revert' (which someone mentioned
> was a good idea at the last GitTogether), and adds 'unstage' for
> 'reset HEAD file'.  also adds a '-s' option to 'branch' to switch to
> the branch after you create it, which many people expect rather than
> 'checkout -b'.

I like 'git unstage', but not the rest.

> * adds 'git resolved' for 'git add', which I hear all the time as
> being confusing

I would prefer 'git stage'; 'git resolved' seems to be meant for a very particular case: resolve conflicts, it would be much better to learn that you can do 'git stage' at any time.

<snip/>

> * 'git backout' for 'git reset HEAD^'

I don't like that. Looks like a very specialized case. It's much better to learn this particular use of 'git reset'.

> * 'git push origin --delete <branch>' for 'git push origin :branch'

That would be really good, it took me a lot of time to find that idiom.

Cheers.

-- 
Felipe Contreras