From: Andreas Ericsson <ae@op5.se>
To: undisclosed-recipients:;
Subject: [PATCH 0/2] Argument order shouldn't matter
Date: Wed, 11 Jan 2006 20:42:58 +0000 (UTC)
Date: 1137012155 +0100 [thread overview]
Message-ID: <20060111204236.0D7E15BEBD@nox.op5.se> (raw)
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
reply other threads:[~2006-01-11 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060111204236.0D7E15BEBD@nox.op5.se \
--to=ae@op5.se \
/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).