From: "Kai Hendry" <hendry@aplixcorp.com>
To: "Mike Hommey" <mh@glandium.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Avery Pennarun" <apenwarr@gmail.com>,
git@vger.kernel.org
Subject: Re: Integration branching
Date: Tue, 8 Apr 2008 21:32:31 +0100 [thread overview]
Message-ID: <b24851260804081332l74beb7e6o2f48b18f65af7b55@mail.gmail.com> (raw)
In-Reply-To: <20080408190127.GA28556@glandium.org>
Hi Mike!
You're busy. :)
So do you acknowledge this as a bug or am I doing something wrong?
If you know where the problem lies, perhaps I can get a C ninja from
work to look at it.
Kind regards from the UK,
next prev parent reply other threads:[~2008-04-08 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 13:02 Integration branching Kai Hendry
2008-04-07 17:41 ` Junio C Hamano
2008-04-07 18:18 ` Kai Hendry
2008-04-07 18:32 ` Avery Pennarun
2008-04-08 13:56 ` Kai Hendry
2008-04-08 18:49 ` Junio C Hamano
2008-04-08 19:01 ` Mike Hommey
2008-04-08 20:32 ` Kai Hendry [this message]
2008-04-08 20:43 ` Mike Hommey
2008-04-10 20:04 ` Mike Hommey
2008-04-07 18:44 ` 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=b24851260804081332l74beb7e6o2f48b18f65af7b55@mail.gmail.com \
--to=hendry@aplixcorp.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mh@glandium.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 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).