git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Dec 2010, #04; Mon, 13)

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 14, 2010, 02:20 UTC
Message-ID
<7vzks9umbn.fsf@alter.siamese.dyndns.org>
In-Reply-To
<AANLkTikGneq+zeN5Z5XrUseX4Arevft67U7pV+h+5Tr+@mail.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
Show 6 quoted lines
> On Mon, Dec 13, 2010 at 09:34, Junio C Hamano <gitster@pobox.com> wrote:
>
>> Needs a bit more minor work to get the basic code structure right.
>
> And I'm still not sure (see earlier replies to "What's Cooking" posts)
> what needs to be done to make it better.

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.

(sorry for a delayed and short response --- have been firefighting elsewhere).

Previous: Ævar Arnfjörð Bjarmason
Message 4 of 4 in “What's cooking in git.git (Dec 2010, #04; Mon, 13)”
  1. Junio C HamanoDec 13, 2010
  2. Sverre RabbelierDec 13, 2010
  3. Ævar Arnfjörð BjarmasonDec 13, 2010
  4. Junio C HamanoDec 14, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.