From: Miklos Vajna <vmiklos@frugalware.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2008, #04; Mon, 29)
Date: Wed, 31 Dec 2008 01:10:36 +0100 [thread overview]
Message-ID: <20081231001036.GW21154@genesis.frugalware.org> (raw)
In-Reply-To: <m3fxk5b6di.fsf@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
On Tue, Dec 30, 2008 at 03:15:43PM -0800, Jakub Narebski <jnareb@gmail.com> wrote:
> P.S. BTW. what is the status on using parse_options among git
> commands?
You mean the C or the shell commands?
I sent the third version of the builtin-apply migration ($gmane/104029),
but I got no answer so far, probably it was dropped on the floor by
accident. ;-)
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-31 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 20:59 What's cooking in git.git (Dec 2008, #04; Mon, 29) Junio C Hamano
2008-12-30 23:15 ` Jakub Narebski
2008-12-31 0:10 ` Miklos Vajna [this message]
2008-12-31 0:22 ` Junio C Hamano
2009-01-03 5:40 ` Christian Couder
2009-01-03 10:31 ` Junio C Hamano
2009-01-04 11:18 ` Christian Couder
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=20081231001036.GW21154@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.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;
as well as URLs for NNTP newsgroup(s).