From: "Santi Béjar" <sbejar@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: Wishlist for a bundle-only transport mode
Date: Fri, 23 Nov 2007 11:13:55 +0100 [thread overview]
Message-ID: <8aa486160711230213q6038037epe2cbd0240db8b612@mail.gmail.com> (raw)
In-Reply-To: <7vejehux3y.fsf@gitster.siamese.dyndns.org>
On Nov 23, 2007 10:31 AM, Junio C Hamano <gitster@pobox.com> wrote:
>
> I was disagreeing with Santi's "'push --bundle' and 'bundle
> create' can be equivalent". They can't be, as "push" is always
> "update" and never "create". So I do not quite get your "But for
> that I think"; I think you are just agreeing with me.
>
> Even if we taught "push" to create (which I doubt would happen
> due to its security and administrative implications), it would
> not make the two any closer to being equivalent. For them to
> become equivalent, we would need to have "push" unlearn how to
> update, which would never happen ;-).
>
OK. So git push will never understand bundles.
My motivation was to have a similar workflow with bundles as with
pushes, or at least as similar as possible. So another possible
workflow would be with a:
git bundle push [<bundle> [<refspec>]]
that creates a bundle
# Have a project with different branches (master, next, pu)
$ git bundle push bundle.bdl
# would create a complete bundle.bdl with all the local branches (with HEAD)
# You send it to the other person and he does:
$ git clone bundle.bdl project
$ cat .git/config
...
[remote "origin"]
url = /path/to/bundle.bdl
fetch = +refs/heads/*:refs/remotes/origin/*
# He makes changes, commits and so on and then he wants to send to back a bundle
$ git bundle push [<remote>]
# This creates an incremental bundle with the local branches (with
HEAD) as specified
# by remote.<remote>.* (possibly with an implicit "push" line
"refs/heads/*:refs/heads/*"
# And considering the remotes/origin/* as the bases for the bundle
# Then I got it and do a:
$ git remote add bundle /path/to/bundle
$ git fetch
# Now maybe I just want to send him the master branch
$ git bundle push origin master:master
# If I want to send him a complete bundle
$ git bundle push
The important part, for me, is to keep remote tracking branches to
know the bases for the next bundle. It does not matter if it is "git
push", "git bundle push", "git push --bundle", "git bundle update",
...
Santi
next prev parent reply other threads:[~2007-11-23 10:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 14:54 Wishlist for a bundle-only transport mode Santi Béjar
2007-11-21 15:04 ` Jakub Narebski
2007-11-21 15:24 ` Santi Béjar
2007-11-21 15:46 ` Johannes Schindelin
2007-11-21 16:52 ` Jakub Narebski
2007-11-21 16:59 ` Johannes Schindelin
2007-11-21 17:11 ` Jakub Narebski
2007-11-21 17:26 ` Johannes Schindelin
2007-11-21 17:52 ` Jakub Narebski
2007-11-22 9:42 ` Santi Béjar
2007-11-22 10:02 ` Junio C Hamano
2007-11-23 9:18 ` Jakub Narebski
2007-11-23 9:31 ` Junio C Hamano
2007-11-23 10:04 ` Jakub Narebski
2007-11-23 10:13 ` Santi Béjar [this message]
2007-11-23 12:18 ` Johannes Schindelin
2007-11-23 15:06 ` Junio C Hamano
2007-11-23 15:34 ` Santi Béjar
2007-11-23 16:05 ` Junio C Hamano
2007-11-23 16:39 ` Santi Béjar
2007-11-24 19:15 ` Junio C Hamano
2007-11-23 19:09 ` Jakub Narebski
2007-11-21 15:59 ` Johannes Schindelin
2007-11-21 16:15 ` Santi Béjar
2007-11-21 16:36 ` Johannes Schindelin
2007-11-21 16:44 ` Santi Béjar
2007-11-21 16:53 ` [PATCH] bundle create: keep symbolic refs' names instead of resolving them Johannes Schindelin
2007-11-22 12:03 ` Johannes Schindelin
2007-11-22 12:24 ` [REPLACEMENT PATCH] " Johannes Schindelin
2007-11-21 16:23 ` Wishlist for a bundle-only transport mode Kristian Høgsberg
2007-11-21 17:07 ` Johannes Schindelin
2007-11-21 17:06 ` Jakub Narebski
2007-11-21 17:29 ` 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=8aa486160711230213q6038037epe2cbd0240db8b612@mail.gmail.com \
--to=sbejar@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.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).