git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Anderson <ryan@michonline.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: Russell King <rmk@arm.linux.org.uk>, git@vger.kernel.org
Subject: Re: More problems...
Date: Fri, 29 Apr 2005 15:50:55 -0400	[thread overview]
Message-ID: <20050429195055.GE1233@mythryan2.michonline.com> (raw)
In-Reply-To: <20050429182708.GB14202@pasky.ji.cz>

On Fri, Apr 29, 2005 at 08:27:08PM +0200, Petr Baudis wrote:
> Dear diary, on Fri, Apr 29, 2005 at 06:01:27PM CEST, I got a letter
> where Russell King <rmk@arm.linux.org.uk> told me that...
> > rmk@dyn-67:[linux-2.6-rmk]:<1049> cg-update origin
> > `../linux-2.6/.git/objects/00/78aeb85737197a84af1eeb0353dbef74427901' -> `.git/objects/00/78aeb85737197a84af1eeb0353dbef74427901'
> > cp: cannot create link `.git/objects/00/78aeb85737197a84af1eeb0353dbef74427901': File exists
> > 
> > By that time, the object files in the reference tree appear to have
> > a newer timestamp than the corresponding ones in my local tree, and
> > cp -lua fails.
> 
> I'm now away ,unfortunately, and no immediate idea stems to my mind on
> how to fix it. Ideas welcomed - I need to hardlink missing entries from
> one tree to another; it would be enough to be able to just tell cp to
> ignore already present files.
> 
> Could you please try to give cp the -f flag?

Why not just use "rsync" for both remote and local synchronization, and
provide a "relink" command to scan two .git/objects/ repositories and
hardlink matching files together?

With the SHA1 hash, you can even have a --unsafe option that just
compares the has names and does a link based purely off of that and the
stat(2) results of both files.  (I'd expect that a ... safer variant
would extract both files and compare them, but the --unsafe should be
sufficient, in practice, I would think.)

-- 

Ryan Anderson
  sometimes Pug Majere

  reply	other threads:[~2005-04-29 19:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 16:01 More problems Russell King
2005-04-29 16:12 ` Russell King
2005-04-29 17:51   ` Linus Torvalds
2005-04-29 18:27 ` Petr Baudis
2005-04-29 19:50   ` Ryan Anderson [this message]
2005-04-29 20:03     ` Thomas Glanzmann
2005-04-29 20:21     ` Linus Torvalds
2005-04-29 21:07       ` Junio C Hamano
2005-04-29 21:19         ` Russell King
2005-04-29 21:57           ` Anton Altaparmakov
2005-05-02 19:33             ` Petr Baudis
2005-05-02 19:44               ` Dave Kleikamp
2005-05-02 19:51                 ` Thomas Glanzmann
2005-05-02 22:01               ` Anton Altaparmakov
2005-05-02 22:19                 ` Linus Torvalds
2005-05-03  1:48                   ` Petr Baudis
2005-05-03  2:56                     ` Daniel Barkalow
2005-05-03 15:00                     ` Andreas Gal
2005-05-03 19:18                       ` Junio C Hamano
2005-04-29 21:27         ` Daniel Barkalow
2005-04-29 22:01           ` Junio C Hamano
2005-04-30  5:36             ` [PATCH] Split out "pull" from particular methods Daniel Barkalow
2005-05-04  5:54       ` [PATCH] Add git-relink-script, a tool to hardlink two existing repositories Ryan Anderson
2005-05-02 21:13     ` More problems Petr Baudis

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=20050429195055.GE1233@mythryan2.michonline.com \
    --to=ryan@michonline.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@ucw.cz \
    --cc=rmk@arm.linux.org.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).