From: joakim@verona.se
To: emacs-devel@gnu.org
Cc: felipe.contreras@gmail.com
Subject: Re: git-1.8.2 support pulling from and pushing to a bzr branch
Date: Tue, 30 Apr 2013 12:24:06 +0200 [thread overview]
Message-ID: <m34neo9v09.fsf@chopper.vpn.verona.se> (raw)
In-Reply-To: <m338ulowke.fsf@chopper.vpn.verona.se> (joakim@verona.se's message of "Sat, 20 Apr 2013 21:01:53 +0200")
joakim@verona.se writes:
> joakim@verona.se writes:
>
>> David Engster <deng@randomsample.de> writes:
>>
>>> 'joakim' writes:
>>>> I also tried cloning trunk. It takes a long time. The resulting
>>>> directory is 12Gb.
>>>
>>> You have to pack it afterwards using 'git gc --agressive'.
>>
>> I tried this. I took some time. (long enough that I started doing
>> something else) Afterwards the repo was 1gb in total.
>>
>> I'm just reporting so people can have some clue what to expect. I'm
>> impressed it works at all, especially as compared to the various
>> fastimport based approaches.
>
> I tried pushing a small patch to my xwidget branch using
> git-remote-bzr. Pushing times out. I've contacted the author about the
> issue.
I have now pushed a test commit to my xwidget branch using the latest
version of Felipes git-remote-bzr.
https://raw.github.com/felipec/git/fc/master/contrib/remote-helpers/git-remote-bzr
Felipe was very helpful during this test. I think more of us should try
it out now.
>
>>
>>>
>>> -David
>>>
--
Joakim Verona
next prev parent reply other threads:[~2013-04-30 10:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 20:02 git-1.8.2 support pulling from and pushing to a bzr branch Jonas Bernoulli
2013-04-13 22:22 ` John Wiegley
2013-04-15 15:42 ` Γιώργος Κεραμίδας
2013-04-15 19:06 ` David Engster
2013-04-16 16:30 ` Giorgos Keramidas
2013-04-16 17:18 ` Julien Danjou
2013-04-18 18:53 ` joakim
2013-04-18 18:57 ` David Engster
2013-04-19 5:55 ` joakim
2013-04-20 19:01 ` joakim
2013-04-30 10:24 ` joakim [this message]
2013-05-01 6:16 ` Felipe Contreras
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=m34neo9v09.fsf@chopper.vpn.verona.se \
--to=joakim@verona.se \
--cc=emacs-devel@gnu.org \
--cc=felipe.contreras@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.