Re: [PATCH 3/9] for-each-ref: avoid printing each element directly to stdout

From: Duy Nguyen <pclouds@gmail.com>
Date: May 19, 2013, 11:58 UTC
Message-ID: <CACsJy8DEup_oatEwB=-nA6_RGrO=k+urJ7cus4Ngc4GSxxMiNA@mail.gmail.com>
In-Reply-To: <CALkWK0mSxYhJDBzrtfZyKQquqAYJiYj2AFBdk3hdDyQgSW3ZRw@mail.gmail.com>

On Sun, May 19, 2013 at 6:17 PM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

>> [PATCH 3/9] for-each-ref: avoid printing each element directly to stdout
>
> Why did you do this?  Atoms are designed to be independent of each
> other.  I'll keep reading: might find out in a later patch.

Sorry for the lack of explanation in the message. I wanted to discuss about syntax more than code. As you see later down the series, we'll need to process an atom for all refs, then output all refs in the end. We can't do that wihout buffering. -- Duy

$ 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.