From: Jakub Narebski <jnareb@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE qgit-1.3]
Date: Sun, 04 Jun 2006 11:17:46 +0200 [thread overview]
Message-ID: <e5u8fk$ju6$1@sea.gmane.org> (raw)
In-Reply-To: e5bfff550606040155v14565312na26f8c866f0fc32d@mail.gmail.com
Marco Costalba wrote:
> This is qgit-1.3
[...]
> NEW IN THIS RELEASE
>
> Main focus of this release is usability.
>
> The big feature is the use of tabs instead of independent windows.
>
> This change alone could be enough for a release. It's a big rewrite of UI
> code to let browsing revisions and patches quicker and easier.
Of course that is advantage _only_ if the tabs are independend, and one
(usually) doesn't need to view them simultaneously, e.g. side by side.
Just my 3 eurocents ;-)
--
Jakub Narebski
Warsaw, Poland
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE qgit-1.3]
Date: Sun, 04 Jun 2006 11:17:46 +0200 [thread overview]
Message-ID: <e5u8fk$ju6$1@sea.gmane.org> (raw)
In-Reply-To: e5bfff550606040155v14565312na26f8c866f0fc32d@mail.gmail.com
Marco Costalba wrote:
> This is qgit-1.3
[...]
> NEW IN THIS RELEASE
>
> Main focus of this release is usability.
>
> The big feature is the use of tabs instead of independent windows.
>
> This change alone could be enough for a release. It's a big rewrite of UI
> code to let browsing revisions and patches quicker and easier.
Of course that is advantage _only_ if the tabs are independend, and one
(usually) doesn't need to view them simultaneously, e.g. side by side.
Just my 3 eurocents ;-)
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-06-04 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 8:55 [ANNOUNCE qgit-1.3] Marco Costalba
2006-06-04 9:17 ` Jakub Narebski [this message]
2006-06-04 9:17 ` Jakub Narebski
2006-06-04 9:32 ` Marco Costalba
2006-06-05 17:59 ` Pavel Roskin
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='e5u8fk$ju6$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.