From: Nick Hengeveld <nickh@reactrix.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/6] http-push updates
Date: Mon, 13 Mar 2006 16:28:15 -0800 [thread overview]
Message-ID: <20060314002815.GJ3997@reactrix.com> (raw)
In-Reply-To: <7vek16udg6.fsf@assigned-by-dhcp.cox.net>
On Sun, Mar 12, 2006 at 09:21:45PM -0800, Junio C Hamano wrote:
> Repository maintenance tasks:
>
> - create a new repository
> - remove an unneeded branch and tag
> - running repack
In a DAV-only server environment, it seems like there are a few
options for supporting these tasks:
- extend http-push with additional args and/or local config settings.
This approach would be more efficient wrt packs than separate
push and repack steps since packs will all need to be created locally
and then sent; a combined repack/push operation would mean that new
objects will only be sent once as part of a pack.
- add DAV versions of git-init-db/git-branch/git-repack
- extend git-init-db/git-branch/git-repack to be DAV-aware
I like option #1.
> - create new branch (and new tag) -- I think you can already do this
Right - you can create locally and then push that branch/tag or
--all/--tags.
> - (perhaps) running update-server-info
http-push already updates info/refs if it existed before the push
(perhaps that behavior should also be based on a local config setting.)
I would plan to add support for updating objects/info/packs along with
pack/repack support. That should be all the server-info there is to
update, right?
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
prev parent reply other threads:[~2006-03-14 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 4:17 [PATCH 0/6] http-push updates Nick Hengeveld
2006-03-13 5:21 ` Junio C Hamano
2006-03-14 0:28 ` Nick Hengeveld [this message]
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=20060314002815.GJ3997@reactrix.com \
--to=nickh@reactrix.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).