From: Johannes Sixt <j.sixt@viscovery.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2010, #03; Wed, 24)
Date: Thu, 25 Nov 2010 11:41:39 +0100 [thread overview]
Message-ID: <4CEE3D63.2010701@viscovery.net> (raw)
In-Reply-To: <AANLkTi=U=Km28W-xUM0vmRhhYCuhjSxxk5Fk_yhvjz8K@mail.gmail.com>
Am 11/25/2010 10:45, schrieb Ævar Arnfjörð Bjarmason:
> On Thu, Nov 25, 2010 at 04:16, Junio C Hamano <gitster@pobox.com> wrote:
>
>> It is getting ridiculously painful to keep re-resolving the conflicts with
>> other topics in flight, even with the help with rerere.
>>
>> Needs a bit more minor work to get the basic code structure right.
>
> Still waiting on input about what exactly needs to be fixed. See
> <AANLkTikw0+FGJmj7C0B9J_3ZVXrbqCw+UzyP3sqfyVdm@mail.gmail.com.
>
> Is there anything else than that (the builtin.h includes) that you
> think needs work?
One open question was why you do not want to move 'LIB_OBJS += gettext.o'
away from the LIB_OBJS section down to the configuration evaluation
section, i.e., why gettext.o would be different from block-sha1/sha1.o.
-- Hannes
next prev parent reply other threads:[~2010-11-25 10:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 3:16 What's cooking in git.git (Nov 2010, #03; Wed, 24) Junio C Hamano
2010-11-25 3:42 ` Jiang Xin
2010-11-25 9:45 ` Ævar Arnfjörð Bjarmason
2010-11-25 10:35 ` Erik Faye-Lund
2010-11-25 12:00 ` Ævar Arnfjörð Bjarmason
2010-11-25 12:34 ` Erik Faye-Lund
2010-11-25 14:54 ` Erik Faye-Lund
2010-11-25 15:03 ` Erik Faye-Lund
2010-11-25 15:22 ` Erik Faye-Lund
2010-11-25 16:33 ` Ævar Arnfjörð Bjarmason
2010-11-25 17:55 ` Erik Faye-Lund
2010-11-25 18:06 ` Ævar Arnfjörð Bjarmason
2010-11-25 20:02 ` Erik Faye-Lund
2010-11-26 0:40 ` Ævar Arnfjörð Bjarmason
2010-11-25 10:41 ` Johannes Sixt [this message]
2010-11-25 16:26 ` Jakub Narebski
2010-12-03 10:36 ` Thomas Rast
2010-12-03 11:13 ` Jakub Narebski
2010-12-03 11:22 ` Thomas Rast
2010-12-03 13:02 ` Jakub Narebski
2010-12-03 13:06 ` Thomas Rast
2010-12-03 14:12 ` Jakub Narebski
2010-12-03 15:03 ` Thomas Rast
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=4CEE3D63.2010701@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=avarab@gmail.com \
--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 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.