From: Nick Hengeveld <nickh@reactrix.com>
To: git@vger.kernel.org
Subject: [PATCH 0/6] http-push updates
Date: Fri, 10 Mar 2006 20:17:49 -0800 [thread overview]
Message-ID: <20060311041749.GB3997@reactrix.com> (raw)
This series fixes a few http transport and http-push bugs, includes some
refactoring, and adds functionality to update remote server info/refs.
I'm considering future support for initializing a remote repo if the
remote url points to an empty directory and the --force arg is present.
Any thoughts?
I'm also planning to add support for using packs to send updates, and
for updating remote server objects/info/packs. I'm not sure whether it
makes sense to always send packs or to only do so when enough objects
need to be pushed.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next reply other threads:[~2006-03-11 4:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 4:17 Nick Hengeveld [this message]
2006-03-13 5:21 ` [PATCH 0/6] http-push updates Junio C Hamano
2006-03-14 0:28 ` Nick Hengeveld
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=20060311041749.GB3997@reactrix.com \
--to=nickh@reactrix.com \
--cc=git@vger.kernel.org \
/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).