From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2008, #06; Wed, 20)
Date: Thu, 21 Aug 2008 14:10:37 +0200 [thread overview]
Message-ID: <g8jm02$5vh$1@ger.gmane.org> (raw)
In-Reply-To: <7vabf7mcpz.fsf@gitster.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 21.08.2008 02:30:
> Here are the topics that have been cooking. Commits prefixed
> with '-' are only in 'pu' while commits prefixed with '+' are
> in 'next'.
>
> The topics list the commits in reverse chronological order. The topics
> meant to be merged to the maintenance series have "maint-" in their names.
>
> Today's 'pu' does not pass tests for me; it seems my box does not like new
> tests for gitweb somehow.
Mine doesn't either (Kubuntu 7.10, as well as F8 in VM).
Michael
prev parent reply other threads:[~2008-08-21 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 0:30 What's cooking in git.git (Aug 2008, #06; Wed, 20) Junio C Hamano
2008-08-21 1:18 ` Jeff King
2008-08-21 2:30 ` Junio C Hamano
2008-08-21 7:49 ` [PATCH] test-lib: do not remove trash_directory if called with --debug Johannes Schindelin
2008-08-21 8:52 ` Junio C Hamano
2008-08-21 12:55 ` Jeff King
2008-08-21 12:10 ` Michael J Gruber [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='g8jm02$5vh$1@ger.gmane.org' \
--to=michaeljgruber+gmane@fastmail.fm \
--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.