From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: What's in git.git (part #2)
Date: Thu, 01 Jun 2006 11:31:49 +0200 [thread overview]
Message-ID: <e5mc5n$m33$1@sea.gmane.org> (raw)
In-Reply-To: 7v1wu9i608.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Junio C Hamano <junkio@cox.net> writes:
>
>> It's been a while since the last feature release,...
>
> So apparently somehow part #1 (the regular "master has these",
> "next in addition has these" message I occasionally do) is not
> liked by the mailing list. I wonder what's in it that makes it
> dropped on the floor...
I had same problem (message not appearing on list), and as far as
I was able to analyse it was because message accidentally (via unclean
copy'n'paste) had some unusual characters.
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-06-01 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 9:19 What's in git.git (part #2) Junio C Hamano
2006-06-01 9:23 ` Junio C Hamano
2006-06-01 9:31 ` Jakub Narebski [this message]
2006-06-01 11:26 ` Sean
2006-06-01 11:26 ` Sean
2006-06-01 22:51 ` Ryan Anderson
2006-06-02 2:35 ` Shawn Pearce
2006-06-02 6:40 ` Junio C Hamano
2006-06-06 5:39 ` Shawn Pearce
2006-06-06 6:16 ` Junio C Hamano
2006-06-06 8:19 ` Johannes Schindelin
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='e5mc5n$m33$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.