From: Andreas Ericsson <ae@op5.se>
To: pasky@suse.cz
Cc: git@vger.kernel.org, spearce@spearce.org
Subject: Re: [PATCH 3/3] [FYI]git-gui: repo.or.cz-ish fork integration
Date: Thu, 25 Sep 2008 08:15:53 +0200 [thread overview]
Message-ID: <48DB2C99.5060909@op5.se> (raw)
In-Reply-To: <20080925000157.506352696@suse.cz>
pasky@suse.cz wrote:
[ a lot of stuff as an attachment ]
FWIW, I thoroughly like this idea and I'm very excited to see how
it'll work in op5's development environment.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-09-25 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 23:57 [PATCH 0/3] [RFC] Support for publishing projects at central site pasky
2008-09-24 23:57 ` [PATCH 1/3] git web--browse: Add --stdin option support pasky
2008-09-24 23:57 ` [PATCH 2/3] git-gui: Use git web--browse --stdin for safe URL passing pasky
2008-09-24 23:57 ` [PATCH 3/3] [FYI]git-gui: repo.or.cz-ish fork integration pasky
2008-09-25 6:15 ` Andreas Ericsson [this message]
2008-09-25 8:56 ` [PATCH 0/3] [RFC] Support for publishing projects at central site Peter Krefting
2008-09-25 10:24 ` Petr Baudis
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=48DB2C99.5060909@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--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).