From: Jeff Garzik <jgarzik@pobox.com>
To: Ryan Anderson <ryan@michonline.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Add git-relink-script to fix up missing hardlinks
Date: Sun, 26 Jun 2005 14:36:58 -0400 [thread overview]
Message-ID: <42BEF5CA.1060809@pobox.com> (raw)
In-Reply-To: <20050626181516.GC20369@mythryan2.michonline.com>
Ryan Anderson wrote:
> Add git-relink-script
>
> This will scan 2 or more object repositories and look for common objects, check
> if they are hardlinked, and replace one with a hardlink to the other if not.
>
> This version warns when skipping files because of size differences, and
> handle more than 2 repositories automatically.
>
> Signed-off-by: Ryan Anderson <ryan@michonline.com>
Thanks for posting this.
next prev parent reply other threads:[~2005-06-26 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 18:15 [PATCH] Add git-relink-script to fix up missing hardlinks Ryan Anderson
2005-06-26 18:36 ` Jeff Garzik [this message]
2005-06-26 19:07 ` Junio C Hamano
2005-06-26 19:31 ` Junio C Hamano
2005-06-26 19:44 ` Jeff Garzik
2005-06-27 1:11 ` Jan Harkes
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=42BEF5CA.1060809@pobox.com \
--to=jgarzik@pobox.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=ryan@michonline.com \
--cc=torvalds@osdl.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).