git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Meeks <michael.meeks@novell.com>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: git@vger.kernel.org, kendy@novell.com,
	Norbert Thiebaud <nthiebaud@gmail.com>
Subject: Re: libreoffice merge(tool?) issue #3 ... (bogus)
Date: Thu, 24 Feb 2011 16:39:20 +0000	[thread overview]
Message-ID: <1298565560.32648.258.camel@lenovo-w500> (raw)
In-Reply-To: <993F66D7-7659-4AA5-9931-1EB66CAA01DB@silverinsanity.com>

Hi Brian,

	First - it seems that the issue here was entirely bogus, not least
because we had a bug with re-writing these makefiles as we checked them
in; so hopefully only 2 issues pending ;-)

	Anyhow - I tried your kind advice:

On Tue, 2011-02-22 at 10:55 -0500, Brian Gernhardt wrote:
> FYI: `git clone foo bar` will use hard-links to copy the object
> files and is both very fast and space efficient.  (See the
> description of `--local` in git-clone(1), which is used by
> default for local repositories since git 1.5.3.)  It's also
> guaranteed to work while the correctness of `cp -lR` depends
> on implementation details of git.

	Sounds like just what I need. Unfortunately, it didn't clone some of
the pieces I needed; eg. other configured remotes, I ended up with just
'origin' - which was unexpected (and less wonderful than cp -lR ;-).

	Is that a feature ?

	Thanks,

		Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot

  reply	other threads:[~2011-02-24 17:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 15:34 libreoffice merge(tool?) issue #3 Michael Meeks
2011-02-22 15:55 ` Brian Gernhardt
2011-02-24 16:39   ` Michael Meeks [this message]
2011-02-25 10:08     ` libreoffice merge(tool?) issue #3 ... (bogus) Michael J Gruber
2011-02-25 20:55     ` Andres Freund
2011-02-28 14:25       ` copying git repositories Michael Meeks
2011-02-28 15:03         ` Andres Freund
2011-02-28 15:10         ` Brian Gernhardt
2011-02-22 17:30 ` libreoffice merge(tool?) issue #3 Michael J Gruber
2011-02-22 18:14   ` Michael Meeks
2011-02-23 11:18     ` Michael J Gruber
2011-02-23 13:22       ` Michael J Gruber

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=1298565560.32648.258.camel@lenovo-w500 \
    --to=michael.meeks@novell.com \
    --cc=benji@silverinsanity.com \
    --cc=git@vger.kernel.org \
    --cc=kendy@novell.com \
    --cc=nthiebaud@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 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).