From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Santi Béjar" <sbejar@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:04:32 +0100 [thread overview]
Message-ID: <200711231104.32605.jnareb@gmail.com> (raw)
In-Reply-To: <7vejehux3y.fsf@gitster.siamese.dyndns.org>
On Fri, 23 Nov 2007, Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>> On Thu, 22 Nov 2007, Junio C Hamano :
>>> "Santi Béjar" <sbejar@gmail.com> writes:
>>>
>>>> Sorry but I do not understand this. I think this two lines could be equivalent:
>>>>
>>>> git push --bundle bundle.bdl "refs/heads/master:refs/remotes/bundle/master"
>>>> git bundle create bundle.bdl refs/heads/master ^refs/remotes/bundle/master
>>>
>>> Interesting.
>>>
>>> $ git push $something ours:theirs
>>>
>>> has defined semantics for any value of $something.
>>> ...
>>> If bundle.bdl does not exist yet, it is like pushing into a
>>> freshly initialized empty repository.
>>
>> But for that I think "git bundle" should learn new subcommand:
>> "git bundle update", which would use refs existing in given
>> bundle as prerequisites, and either update bundle (create anew
>> or just concatenate next pack) or create incremental bundle.
>>
>> Something similar to incremental mode or update command of
>> archivers...
>
> 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.
Bad choice of words on my part... and I didn't parse that you were
disagreeing as well as commenting. :-/
> 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 ;-).
I also think that pushing to bundle might be not a good idea;
but I think that "git clone <bundle>" should just work.
Nevertheless I think that having "git bundle update" or
"git bundle create --reference=<old bundle>" (or both) would be
a good thing, as it would free us from remembering or tagging when
last bundle was created.
Could anyone who uses "git bundle" actively raise a voice?
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-11-23 10:04 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 [this message]
2007-11-23 10:13 ` Santi Béjar
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=200711231104.32605.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbejar@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 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.