From: Junio C Hamano <gitster@pobox.com>
To: "Santi Béjar" <santi@agolina.net>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"git list" <git@vger.kernel.org>
Subject: Re: git-bpush: Pushing to a bundle
Date: Tue, 09 Dec 2008 09:32:18 -0800 [thread overview]
Message-ID: <7voczl45lp.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: adf1fd3d0812090221t2264a4f9i87b5e23be897ee84@mail.gmail.com
"Santi Béjar" <santi@agolina.net> writes:
> I do not find convenient strictly incremental bundles, because then
> you (or the other people) needs to fetch every single bundle. What I
> do is add new objects until the bundle is too big and then create a
> bundle with a new base. This way you don't have to worry if the other
> person has applied the last bundle or not.
You both have good points. I sort of tend to side with your argument from
convenience point of view, if only because that resembles the way how
people traditionally arrange incremental backups "a full dump on Sunday
night, and every day incremental relative to the last full dump". Dscho's
suggestion is akin to "a full dump on Sunday night, and every day
incremental relative to the previous day". Both form obviously can
recreate the same contents, but often "incremental since the last full
synchronization point", even though it may make bigger dumps, is easier to
handle for humans.
>> IOW if you already have a bundle,
>> you want to create a new bundle that contains everything that is new, _in
>> addition_ to the existing bundle.
>
>>> while [ $# != 0 ] ; do
>>
>> Heh, I did not realize just how _used_ I got to the conventions in Git's
>> shell programming, until I thought "Should this not use 'test' instead
>> of brackets?"
Now I see you are improving ;-)
>>> while [ $# != 0 ] ; do
>>> refs="$refs$LF$1" && shift
>>> done
>>
>> That is equivalent to refs="$*", no?
>
> Almost, IFS is set to line-feed so I needed to put $LF instead of spaces.
If $IFS is set to LF, "$*" will be $1, $2, $3 concatenated with LF in
between. The first character in $IFS is used for that purpose..
prev parent reply other threads:[~2008-12-09 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 9:49 git-bpush: Pushing to a bundle Santi Béjar
2008-12-09 10:07 ` Johannes Schindelin
2008-12-09 10:21 ` Santi Béjar
[not found] ` <493E545B.6010609@viscovery.net>
2008-12-09 14:58 ` Santi Béjar
2008-12-09 17:32 ` Junio C Hamano [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=7voczl45lp.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=santi@agolina.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).