From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Charles Bailey" <charles@hashpling.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Using git for file archival/backup purposes - deletion strategy
Date: Fri, 28 Dec 2007 11:08:20 +1300 [thread overview]
Message-ID: <46a038f90712271408k7763d60ai93491f59c75d0e35@mail.gmail.com> (raw)
In-Reply-To: <4773D498.8040204@hashpling.org>
On Dec 28, 2007 5:36 AM, Charles Bailey <charles@hashpling.org> wrote:
> Martin Langhoff wrote:
> > Ah! Local clones won't honour --depth!. A clone from git.kernel.org
> > does get its .git/shallow file.
>
> This should be fixed in git v1.5.4-rc0 and later. For reference
> what version of git are you using?
Good point. I was using a 1.5.3xx. I can confirm it's fixed with
1.5.4.rc1.1136.g2794f - I get the shallow clone I expected.
cheers!
m
prev parent reply other threads:[~2007-12-27 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 22:43 Using git for file archival/backup purposes - deletion strategy Martin Langhoff
2007-12-27 9:18 ` Johannes Sixt
2007-12-27 16:36 ` Charles Bailey
2007-12-27 22:08 ` Martin Langhoff [this message]
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=46a038f90712271408k7763d60ai93491f59c75d0e35@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=charles@hashpling.org \
--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).