From: "Marco Costalba" <mcostalba@gmail.com>
To: "Steffen Prohaska" <prohaska@zib.de>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: qgit 2.1 questions about range selection
Date: Tue, 1 Jan 2008 16:33:59 +0100 [thread overview]
Message-ID: <e5bfff550801010733k63ed0c3du273f28b684efe904@mail.gmail.com> (raw)
In-Reply-To: <771EDDAF-F479-45F7-AB85-F7B6603FB061@zib.de>
On Dec 31, 2007 11:42 AM, Steffen Prohaska <prohaska@zib.de> wrote:
>
> Here is a first impressions and some questions about the range
> selection, which I find pretty hard to understand.
>
Hi Steffen,
I have just pushed to
git://git.kernel.org/pub/scm/qgit/qgit4.git
a patch series that should address some of your concerns.
More questions are welcomed ;-)
Marco
next prev parent reply other threads:[~2008-01-01 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <771EDDAF-F479-45F7-AB85-F7B6603FB061@zib.de>
[not found] ` <e5bfff550712310352j3245511chbbd301d35e09204b@mail.gmail.com>
2007-12-31 11:53 ` Fwd: qgit 2.1 questions about range selection Marco Costalba
2008-01-01 15:33 ` Marco Costalba [this message]
2008-01-01 20:03 ` Steffen Prohaska
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=e5bfff550801010733k63ed0c3du273f28b684efe904@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.de \
/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).