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

[PATCH 0/2] Argument order shouldn't matter

From
Andreas Ericsson <ae@op5.se>
Date
Jan 11, 2006, 20:42 UTC
Message-ID
<20060111204236.0D7E15BEBD@nox.op5.se>

Many of the C-programs in the git suite are sensitive to argument ordering. That's a bit backwards for a modern tool-kit.

The first of these two patches provides some simple library code to handle arbitrary pointers in a stack-like manner, although in addition to stack_push() and stack_pop(), with their obvious meanings, there's also stack_pull() which fetches from the bottom of the stack. Err... that is, it fetches the least recently pushed item first.

The second patch is just an example of its implementation so we can get the discussions going.

--
 Makefile   |    4 ++--
 describe.c |   15 ++++++++++-----
 stack.c    |   42 ++++++++++++++++++++++++++++++++++++++++++
 stack.h    |    9 +++++++++
 4 files changed, 63 insertions(+), 7 deletions(-)
--
git version 1.1.0
Message 1 of 1 in “Argument order shouldn't matter”
  1. 0/2 Argument order shouldn't matterAndreas Ericsson, Jan 11, 2006

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.