From: Michael J Gruber <git@drmicha.warpmail.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2009, #01; Fri, 12)
Date: Fri, 12 Jun 2009 16:19:01 +0200 [thread overview]
Message-ID: <4A3263D5.7030704@drmicha.warpmail.net> (raw)
In-Reply-To: <7v1vppbyud.fsf@alter.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 12.06.2009 11:11:
> * mg/pushurl (Tue Jun 9 18:01:38 2009 +0200) 5 commits
> - builtin-remote: Make "remote -v" display push urls
> - builtin-remote: Show push urls as well
> - technical/api-remote: Describe new struct remote member pushurl
> - t5516: Check pushurl config setting
> - Allow push and fetch urls to be different
>
> Will merge to 'next' soon.
I'll rewrite the commit message of 5/5 as we discussed. Sorry for the
lag, I'm in the middle of switching from Fedora 10 to 11 (while being
sick for other reasons) ...
Michael
next prev parent reply other threads:[~2009-06-12 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 9:11 What's cooking in git.git (Jun 2009, #01; Fri, 12) Junio C Hamano
2009-06-12 10:04 ` Thomas Rast
2009-06-12 14:19 ` Michael J Gruber [this message]
2009-06-12 18:38 ` Brandon Casey
2009-06-12 19:40 ` Junio C Hamano
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=4A3263D5.7030704@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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