From: Pat Thoyts <patthoyts@users.sourceforge.net>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Gustaf Hendeby <hendeby@isy.liu.se>,
git@vger.kernel.org
Subject: Re: [PATCH 1/3] git-gui: fix typo in image data
Date: Fri, 28 Jan 2011 09:34:08 +0000 [thread overview]
Message-ID: <87zkql5q3z.fsf@fox.patthoyts.tk> (raw)
In-Reply-To: <c373e73fb114ebc580c36bc494dc62f80a19ece9.1291927374.git.bert.wesarg@googlemail.com> (Bert Wesarg's message of "Thu, 9 Dec 2010 21:46:21 +0100")
This patchset look fine - thank you, applying to master.
--
Pat Thoyts http://www.patthoyts.tk/
PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD
prev parent reply other threads:[~2011-01-28 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 20:46 [PATCH 1/3] git-gui: fix typo in image data Bert Wesarg
2010-12-09 20:46 ` [PATCH 2/3] git-gui: remove 'no such variable' for s error when encounter unknown file states Bert Wesarg
2010-12-09 20:46 ` [PATCH 3/3] git-gui: learn more type change states Bert Wesarg
2011-01-28 9:34 ` Pat Thoyts [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=87zkql5q3z.fsf@fox.patthoyts.tk \
--to=patthoyts@users.sourceforge.net \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=hendeby@isy.liu.se \
--cc=spearce@spearce.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 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).