From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: Users of git-check-files?
Date: Wed, 03 Aug 2005 10:37:12 -0700 [thread overview]
Message-ID: <7virymdirb.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0508031014070.3258@g5.osdl.org> (Linus Torvalds's message of "Wed, 3 Aug 2005 10:23:14 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> I started out to make the "-f" flag to send-file work around it, but I
> never finished that, partly because it really ends up being the same thing
> as "git-fetch-pack" in reverse, which was against the whole point of
> git-send-pack. Send-pack is meant to be an "update remote tree" thing,
> with the assumption that the remote tree is a subset - and exactly that
> assumption is what makes send-pack much cheaper than fetch-pack.
I think in addition to the existing ref_newer() check, which
makes sure you are advancing the remote head, not just replacing
with something unrelated, making sure that we have objects
referenced by ref->old_sha1 we obtained from the remote on our
end for all branches involved would be the only thing needed.
The latter the users should not even be able to override with
the --force flag, of course, but we would remind them to pull
from the other end first.
next prev parent reply other threads:[~2005-08-03 17:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 23:10 Users of git-check-files? Johannes Schindelin
2005-08-03 2:43 ` Linus Torvalds
2005-08-03 6:17 ` Junio C Hamano
2005-08-03 14:21 ` Johannes Schindelin
2005-08-03 18:00 ` Linus Torvalds
2005-08-03 22:09 ` Johannes Schindelin
2005-08-03 15:09 ` Linus Torvalds
2005-08-03 15:51 ` Junio C Hamano
2005-08-03 16:17 ` Linus Torvalds
2005-08-03 16:36 ` Junio C Hamano
2005-08-03 16:45 ` Linus Torvalds
2005-08-03 16:50 ` Johannes Schindelin
2005-08-03 17:08 ` Josef Weidendorfer
2005-08-03 17:30 ` Junio C Hamano
2005-08-03 17:46 ` Josef Weidendorfer
2005-08-03 18:08 ` Linus Torvalds
2005-08-03 23:25 ` [PATCH] (preview) Renaming push Junio C Hamano
2005-08-03 23:48 ` Linus Torvalds
2005-08-04 0:05 ` Junio C Hamano
2005-08-04 0:13 ` Linus Torvalds
2005-08-04 1:02 ` Junio C Hamano
2005-08-04 5:26 ` Junio C Hamano
2005-08-04 5:42 ` Linus Torvalds
2005-08-04 8:09 ` Junio C Hamano
2005-08-04 9:34 ` [PATCH] Teach rev-list since..til notation Junio C Hamano
2005-08-03 18:02 ` Users of git-check-files? Linus Torvalds
2005-08-03 17:02 ` Junio C Hamano
2005-08-03 17:23 ` Linus Torvalds
2005-08-03 17:37 ` Junio C Hamano [this message]
2005-08-03 17:46 ` Josef Weidendorfer
2005-08-03 18:10 ` Linus Torvalds
2005-08-03 17:48 ` Linus Torvalds
2005-08-03 18:07 ` Junio C Hamano
2005-08-03 18:31 ` Josef Weidendorfer
2005-08-03 16:46 ` Johannes Schindelin
2005-08-04 20:59 ` Junio C Hamano
2005-08-04 21:10 ` Johannes Schindelin
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=7virymdirb.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.