From: Mark Levedahl <mdl123@verizon.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer
Date: Sat, 17 Feb 2007 09:40:00 -0500 [thread overview]
Message-ID: <45D713C0.1010401@verizon.net> (raw)
In-Reply-To: <7vfy95w9sc.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> I do not think your patch (original or respun) checks if it is
> overwriting the current branch. Even if it is a fast forward,
> it should check this condition and prevent the end user from
> getting confused. The above sample command line you quoted from
> my message can potentially have the same problem, but "git
> fetch" checks and refuses.
>
True. I've been using this to mirror remote/* and tags. Making this just
an alternate transport behind fetch and pull is clearly the cleanest way
to deal with non-remote branches.
> A final note. A real 'mirror' mode should also remove stale
> refs that do not exist on the remote side anymore, which is a
> different use case as your bundle, which presumably is primarily
> meant to carry not all but only selected set of refs, and most
> likely not the 'master' branch head (and I am guessing that that
> is why you forgot to make sure you are not overwriting the
> current branch in the unbundle script). A real 'mirror' mode
> would use a separate option to remove a ref that does not exist
> on the remote end anymore, like:
>
> $ git fetch --mirror-all git://git.kernel.org/pub/scm/git/git.git
>
Perhaps "git fetch --mirror --delete" would be more suggestive of the
difference to "git fetch --mirror"?
Mark
next prev parent reply other threads:[~2007-02-17 14:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 12:53 Re: [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer Mark Levedahl
2007-02-16 19:57 ` Junio C Hamano
2007-02-16 23:21 ` Mark Levedahl
2007-02-17 6:57 ` Junio C Hamano
2007-02-17 14:40 ` Mark Levedahl [this message]
2007-02-17 17:53 ` Junio C Hamano
2007-02-17 14:50 ` Mark Levedahl
2007-02-17 18:41 ` Junio C Hamano
2007-02-18 17:27 ` [PATCH] Add git-bundle: move objects and references by archive Mark Levedahl
2007-02-18 22:47 ` Mark Levedahl
2007-02-16 21:58 ` [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer Mark Levedahl
2007-02-16 22:51 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2007-02-16 0:19 Respun - Scripts to use bundles to move data between repos Mark Levedahl
2007-02-16 0:19 ` [PATCH] Add git-bundle - pack objects and references for disconnected transfer Mark Levedahl
2007-02-16 0:19 ` [PATCH] Add git-unbundle - unpack " Mark Levedahl
2007-02-16 2:24 ` Junio C Hamano
2007-02-16 2:40 ` Linus Torvalds
2007-02-16 6:38 ` Mark Levedahl
2007-02-16 6:48 ` Shawn O. Pearce
2007-02-16 7:31 ` Junio C Hamano
2007-02-16 7:45 ` Shawn O. Pearce
2007-02-16 6:22 ` Mark Levedahl
2007-02-16 7:24 ` 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=45D713C0.1010401@verizon.net \
--to=mdl123@verizon.net \
--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).