From: Phil Hord <hordp@cisco.com>
To: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Cc: Phil Hord <hordp@cisco.com>
Subject: [PATCH 0/1] transport: Use is_bundle instead of !is_gitfile
Date: Thu, 13 Oct 2011 16:26:01 -0400 [thread overview]
Message-ID: <1318537562-18581-1-git-send-email-hordp@cisco.com> (raw)
I'm not sure where this patch should go now since I see my
original patchset on both next and pu. Should I re-roll the
original series with this one merged in, or just submit this
one isolated, as I am doing here?
Pardon my newbieness.
Phil Hord (1):
transport: Add is_bundle() to detect bundle urls
bundle.c | 16 ++++++++++++++++
bundle.h | 1 +
transport.c | 10 +---------
3 files changed, 18 insertions(+), 9 deletions(-)
--
1.7.7.334.g311c9.dirty
next reply other threads:[~2011-10-13 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 20:26 Phil Hord [this message]
2011-10-13 20:26 ` [PATCH 1/1] transport: Add is_bundle() to detect bundle urls Phil Hord
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=1318537562-18581-1-git-send-email-hordp@cisco.com \
--to=hordp@cisco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).