From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
Junio C Hamano <gitster@pobox.com>,
Scott Chacon <schacon@gmail.com>,
Sam Vilain <sam.vilain@catalyst.net.nz>,
Petr Baudis <pasky@suse.cz>
Subject: Re: GitTogether topics status (4th of October)
Date: Fri, 17 Oct 2008 21:18:16 +0200 [thread overview]
Message-ID: <48F8E4F8.3050902@lsrfire.ath.cx> (raw)
In-Reply-To: <200810041816.41026.chriscool@tuxfamily.org>
Christian Couder schrieb:
> Hi,
>
> As can be seen on the GitTogether page on the wiki:
>
> http://git.or.cz/gitwiki/GitTogether
While I won't be there, another good topic might be the usage of a patch
tracker like patchwork (http://ozlabs.org/~jk/projects/patchwork/).
René
prev parent reply other threads:[~2008-10-17 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 16:16 GitTogether topics status (4th of October) Christian Couder
2008-10-07 3:15 ` Jeff King
2008-10-07 3:46 ` Nicolas Pitre
2008-10-07 14:38 ` Shawn O. Pearce
2008-10-07 14:46 ` Shawn O. Pearce
2008-10-17 19:18 ` René Scharfe [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=48F8E4F8.3050902@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
--cc=sam.vilain@catalyst.net.nz \
--cc=schacon@gmail.com \
--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).