git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Roger Gammans <roger@gammascience.co.uk>
Cc: git@vger.kernel.org
Subject: Re: how to reduce disk usage for large .git dirs?
Date: Thu, 13 Nov 2014 13:21:20 +0100	[thread overview]
Message-ID: <20141113122119.GC15503@aepfle.de> (raw)
In-Reply-To: <1415880149.4825.43.camel@knuth.computer-surgery.co.uk>

On Thu, Nov 13, Roger Gammans wrote:

> Note the first sentence of the second paragraph.
>  eg:
>  # git clone git://host/repo.git repo-master
>  # git clone repo-master repo-branchA
>  # cd repo-branchA
>  # git checkout -b branchA origin/branchA

It fails right here because in this dir only "master" exists, but
branchA is expected.

So far the sequence of commands is:

# git clone git://host/repo.git repo-master
# cd repo-master
# git checkout -b branchA origin/branchA
# git checkout -b branchB origin/branchB
# cd -
# git clone -l -b branchA repo-master repo-branchA
# git clone -l -b branchB repo-master repo-branchB

Next step will be:
# $do_work ; git commit -avs ; git push 

Will that work as expected? Will find out after lunch..


Olaf

  reply	other threads:[~2014-11-13 12:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 11:14 how to reduce disk usage for large .git dirs? Olaf Hering
2014-11-13 11:49 ` Fredrik Gustafsson
2014-11-13 12:03   ` Olaf Hering
2014-11-14 12:32     ` Jakub Narębski
2014-11-13 12:02 ` Roger Gammans
2014-11-13 12:21   ` Olaf Hering [this message]
2014-11-13 12:09 ` Duy Nguyen
2014-11-13 15:44 ` Olaf Hering
2014-11-13 16:03   ` Fredrik Gustafsson
2014-11-13 16:08     ` Johan Herland
2014-11-13 20:15       ` Jeff King
2014-11-14 10:14     ` Olaf Hering
2014-11-14 10:24       ` Fredrik Gustafsson
2014-11-14 10:30         ` Olaf Hering
2014-11-14 10:54           ` Olaf Hering
2014-11-14 11:24     ` Olaf Hering
2014-11-14 15:06       ` Andreas Schwab
2014-11-25 14:32         ` Olaf Hering

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=20141113122119.GC15503@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=git@vger.kernel.org \
    --cc=roger@gammascience.co.uk \
    /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).