From: Santi Bejar <sbejar@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Pure renames/copies
Date: Tue, 22 Nov 2005 10:03:03 +0100 [thread overview]
Message-ID: <8aa486160511220103t7caf5ad2n@mail.gmail.com> (raw)
In-Reply-To: <7vacfxrdao.fsf@assigned-by-dhcp.cox.net>
>
> Probably something like this would suffice.
>
Ok, thanks. Now the only issue with my broken repository (it does not
have all the blobs) is that it outputs:
error: unable to find abcde....
for all the src paths, but the result is ok.
But I can live with it.
Thanks
prev parent reply other threads:[~2005-11-22 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 12:01 Pure renames/copies Santi Béjar
2005-11-21 18:37 ` Linus Torvalds
2005-11-21 19:31 ` Junio C Hamano
2005-11-21 19:50 ` Junio C Hamano
2005-11-21 21:01 ` H. Peter Anvin
2005-11-21 21:33 ` Junio C Hamano
2005-11-21 21:37 ` H. Peter Anvin
2005-11-21 22:00 ` Junio C Hamano
2005-11-21 22:10 ` H. Peter Anvin
2005-11-21 22:17 ` H. Peter Anvin
2005-11-22 9:03 ` Santi Bejar [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=8aa486160511220103t7caf5ad2n@mail.gmail.com \
--to=sbejar@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).