From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Jonas Fonseca <jonas.fonseca@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [tig PATCH] Predefined external command: git commit
Date: Sat, 21 Feb 2009 19:52:00 +0100 [thread overview]
Message-ID: <cb7bb73a0902211052s554e20d7pa412613f56cbf86d@mail.gmail.com> (raw)
In-Reply-To: <2c6b72b30902210951m619c7cf9qa505883f43128e44@mail.gmail.com>
On Sat, Feb 21, 2009 at 6:51 PM, Jonas Fonseca <jonas.fonseca@gmail.com> wrote:
> On Sat, Feb 21, 2009 at 18:19, Giuseppe Bilotta
> <giuseppe.bilotta@gmail.com> wrote:
>> Thank you for this excellent piece of software. I have some more minor
>> patches up at git://git.oblomov.eu/tig (gitweb at same address with
>> http) which I'm going to submit soon.
>
> Don't bother sending the `tig log` patch. ;)
>
> I deprecated this subcommand a long time ago, and would prefer if it
> wasn't added again. Having a lot of subcommands makes it more likely
> that doing `tig $BRANCH` will not do the expected thing. Also, I don't
> find it particularly useful myself and might actually remove it in the
> future, if I ever get to implementing support for defining "custom
> views".
You actually plan on removing the log view altogether?
The problem of conflicting with tig $BRANCH could maybe be solved by
prefixing commands with something (a dot or something easy to type, if
not the traditional - or --)
>> I honestly wish I could contribute with some more important feature
>> such as bundle support or automatic color inversion on light
>> backgrounds.
>
> /me too. :)
I'll do my best 8-)
--
Giuseppe "Oblomov" Bilotta
prev parent reply other threads:[~2009-02-21 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 0:28 [tig PATCH] Predefined external command: git commit Giuseppe Bilotta
2009-02-21 16:19 ` Jonas Fonseca
2009-02-21 17:19 ` Giuseppe Bilotta
2009-02-21 17:51 ` Jonas Fonseca
2009-02-21 18:52 ` Giuseppe Bilotta [this message]
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=cb7bb73a0902211052s554e20d7pa412613f56cbf86d@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.org \
--cc=jonas.fonseca@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).