All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dirk Süsserott" <poststelle@suesserott.de>
To: "Dirk Süsserott" <newsletter@dirk.my1.cc>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git gui: Possible to see which commands are executed?
Date: Sun, 18 May 2008 14:34:37 +0200	[thread overview]
Message-ID: <4830225D.5050605@suesserott.de> (raw)
In-Reply-To: <20080518121349.GE27724@genesis.frugalware.org>

Miklos Vajna schrieb:
> On Sun, May 18, 2008 at 02:03:35PM +0200, Dirk Süsserott <newsletter@dirk.my1.cc> wrote:
>   
>> I'm not aware that such a thing as "git branch rename"
>> exists on the command line.
>>     
>
> man git-branch, search for rename:
>
> "With a -m or -M option, <oldbranch> will be renamed to <newbranch>."
>   
Thanks. Ok, I missed that "rename branch" switch :-(. But that was just 
an example.
I'm actually looking for a 'git gui --log' switch to show me your very 
answer.

  reply	other threads:[~2008-05-18 12:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18 12:03 git gui: Possible to see which commands are executed? Dirk Süsserott
2008-05-18 12:13 ` Miklos Vajna
2008-05-18 12:34   ` Dirk Süsserott [this message]
2008-05-19  2:21 ` Shawn O. Pearce
2008-05-20 19:03   ` Dirk Süsserott
2008-05-20 19:44     ` Shawn O. Pearce
2008-05-20 20:05       ` Sverre Rabbelier
2008-05-20 20:17         ` Shawn O. Pearce
2008-05-20 20:22           ` Sverre Rabbelier
2008-05-20 20:31             ` Shawn O. Pearce
2008-05-20 20:46               ` Sverre Rabbelier
2008-05-20 21:34               ` Junio C Hamano
2008-05-21  2:41                 ` Shawn O. Pearce
2008-05-21  8:30                   ` Johannes Schindelin
2008-05-21  9:27                     ` Karl Hasselström
2008-05-22 12:12                     ` Shawn O. Pearce
2008-05-22 20:55               ` Nigel Magnay
2008-05-22 23:05                 ` Shawn O. Pearce
2008-05-20 20:12       ` Dirk Süsserott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4830225D.5050605@suesserott.de \
    --to=poststelle@suesserott.de \
    --cc=git@vger.kernel.org \
    --cc=newsletter@dirk.my1.cc \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.