From: Pierre Habouzit <madcoder@debian.org>
To: git@vger.kernel.org
Subject: Re: git subscribe
Date: Wed, 30 Jan 2008 23:09:22 +0100 [thread overview]
Message-ID: <20080130220922.GL15004@artemis.madism.org> (raw)
In-Reply-To: <47A0ED98.1000801@vivisimo.com>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
On Wed, Jan 30, 2008 at 09:35:20PM +0000, Jake Goulding wrote:
> git subscribe
$ git subscribe
git: 'subscribe' is not a git-command. See 'git --help'.
Damn … maybe we should make it a git builtin ?
SCNR
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-30 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 21:35 git subscribe Jake Goulding
2008-01-30 22:09 ` Pierre Habouzit [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-07 1:06 Aaron Hall
2021-07-09 9:50 ` Philip Oakley
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080130220922.GL15004@artemis.madism.org \
--to=madcoder@debian.org \
--cc=git@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).