Re: git gui: Possible to see which commands are executed?

From: Sverre Rabbelier <alturin@gmail.com>
Date: May 20, 2008, 20:22 UTC
Message-ID: <bd6139dc0805201322r6c8dae8cy45d31af6c25fd25a@mail.gmail.com>
In-Reply-To: <20080520201722.GF29038@spearce.org>

On Tue, May 20, 2008 at 10:17 PM, Shawn O. Pearce <spearce@spearce.org> wrote:

Show 7 quoted lines

> Yup.  Or even worse, a user thinking that the best way to create a
> new commit on the command line is the ugly sequence of:
>
>        git-write-tree
>        git-commit-tree ... -p ... <msg
>        git-update-ref HEAD ...
>

That would be awesome, no wait.. it wouldn't :P.

Show 7 quoted lines

>> Even better of course would be to not only print the plumbing commands
>> but also the porcelain commands!
>
> That is probably difficult.  Some of the code internally is more
> about stringing the right sequence of plumbing together than it
> is about a particular user action.  I think it would take a bit of
> work to make it do this, and I just don't see a reason to do it.

The reason would be to make the switch from using git-gui only to using the commandline too... the again, it'd be cutting your own hand (or is it "throat" in English...) to make that transition easier.

> CVS clients that show CVS commands can easily do so, because they
> are directly executing the commands they show you.  This is likely
> also true of SVN commands.  But git-gui on Git, that's a whole
> different animal.

Ah, I didn't realise git-gui does stuff that you can't really do through the regular porcelain. In that case it would indeed be impossible to print the regular porcelain commands. I think the '--trace' option should be advertised as 'debugging option' so that the user can see what is going on in the case something goes wrong perhaps?

-- 
Cheers,

Sverre Rabbelier