git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "git discussion list" <git@vger.kernel.org>
Subject: Re: how to combine two clones in a collection
Date: Tue, 10 Jul 2007 19:51:11 +1200	[thread overview]
Message-ID: <46a038f90707100051l5f226799sa8f3231b1c096722@mail.gmail.com> (raw)
In-Reply-To: <20070710062104.GA22603@piper.oerlikon.madduck.net>

On 7/10/07, martin f krafft <madduck@madduck.net> wrote:
> It does mean, however, that I duplicate the upstream into my repo,
> and thus into the published repo at git.debian.org, because I cannot
> just publish a single branch ('debian') in such a way that people
> could clone it and still be able to build the package against
> upstream (which they'd have to obtain for themselves), right?

Yes. But is that a problem? In most cases, the complete history of the
project is fairly small if your repo is well packed. Often not much
bigger than a tarball of one source snapshot.

What does the following say?

   git repack -a -d
   du -sh .git/objects/pack

cheers,


martni

  parent reply	other threads:[~2007-07-10  7:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 22:22 how to combine two clones in a collection martin f krafft
2007-07-10  2:35 ` Linus Torvalds
2007-07-10  6:21   ` martin f krafft
2007-07-10  7:17     ` Junio C Hamano
2007-07-10  7:40       ` martin f krafft
2007-07-10  7:51     ` Martin Langhoff [this message]
2007-07-10 17:05     ` Linus Torvalds
2007-07-10 17:45       ` martin f krafft
2007-07-10 18:27         ` Brian Gernhardt
2007-07-10 19:27           ` Kalle Pokki
2007-07-10 20:00             ` Brian Gernhardt
2007-07-10 23:45               ` Robin Rosenberg
2007-07-11 18:13                 ` martin f krafft
2007-07-11 18:37                   ` Johannes Schindelin
2007-07-11 19:22                     ` martin f krafft
2007-07-11 10:46         ` Jakub Narebski

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=46a038f90707100051l5f226799sa8f3231b1c096722@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    /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).