public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail•com>
To: git@vger•kernel.org
Cc: Junio C Hamano <gitster@pobox•com>
Subject: [RFC 0/3] Alternates API
Date: Wed, 30 Mar 2011 21:40:43 +0000	[thread overview]
Message-ID: <cover.1301521243.git.mfwitten@gmail.com> (raw)
In-Reply-To: 3c357acd119aa836f6cd3298d62cc5098f4c053c.1301521244.git.mfwitten@gmail.com

Michael Witten (3):
  Alternates API: Untangle the interface
  Alternates API: Improve naming
  Alternates API: Remove unused parameter

 builtin/fetch-pack.c   |    9 +++++++--
 builtin/receive-pack.c |    9 +++++++--
 cache.h                |    4 ++--
 sha1_file.c            |    8 ++++----
 transport.c            |   11 +++++------
 transport.h            |    4 ++--
 6 files changed, 27 insertions(+), 18 deletions(-)

-- 
1.7.4.18.g68fe8

  reply	other threads:[~2011-03-30 22:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 15:28 [RFC 2/2] Future Proofing: Pass around pointers to either functions or data Michael Witten
2011-03-29 15:02 ` [RFC 1/2] Portability: Convert strictly between function pointers Michael Witten
2011-03-30 10:09 ` [RFC 2/2] Future Proofing: Pass around pointers to either functions or data Erik Faye-Lund
2011-03-30 15:02   ` Michael Witten
2011-03-30 19:41   ` Junio C Hamano
2011-03-30 21:24 ` [RFC 2/3] Alternates API: Improve naming Michael Witten
2011-03-30 21:28   ` [RFC 3/3] Alternates API: Remove unused parameter Michael Witten
2011-03-30 21:40     ` Michael Witten [this message]
2011-03-30 20:43       ` [RFC 1/3] Alternates API: Untangle the interface Michael Witten
2011-03-30 22:28         ` Junio C Hamano
2011-03-30 22:46     ` [RFC 3/3] Alternates API: Remove unused parameter Junio C Hamano
2011-03-30 22:31   ` [RFC 2/3] Alternates API: Improve naming Junio C Hamano

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=cover.1301521243.git.mfwitten@gmail.com \
    --to=mfwitten@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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