From: Jonathan Nieder <jrnieder@gmail.com>
To: Drew Northup <drew.northup@maine.edu>
Cc: Alexei Sholik <alcosholik@gmail.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: 'typechange' in the git-status output
Date: Mon, 14 Mar 2011 14:22:38 -0500 [thread overview]
Message-ID: <20110314192238.GA30378@elie> (raw)
In-Reply-To: <1300129161.13980.4.camel@drew-northup.unet.maine.edu>
Hi,
Drew Northup wrote:
> As has been said more than a few times (and is probably somewhere in the
> docs), if you really want to duplicate a git repo you should probably be
> using git to do it.
FWIW I don't agree with this advice. "cp -a" works perfectly well and
I think that's a valuable thing.
On the other hand, if you want to _back up_ or sneakernet a git repo,
I agree that "git bundle create /path/to/backup.bundle --all" is
better.
Perhaps the user manual could explain this somewhere.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2011-03-14 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 18:29 'typechange' in the git-status output Alexei Sholik
2011-03-14 18:39 ` Jeff King
2011-03-14 18:39 ` Alexei Sholik
2011-03-14 18:59 ` Drew Northup
2011-03-14 19:22 ` Jonathan Nieder [this message]
2011-03-14 19:27 ` Jeff King
2011-03-14 19:44 ` Junio C Hamano
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=20110314192238.GA30378@elie \
--to=jrnieder@gmail.com \
--cc=alcosholik@gmail.com \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=peff@peff.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).