From: Paul Jakma <paul@clubi.ie>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: On recording renames
Date: Sat, 4 Mar 2006 04:09:44 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0603040405260.13612@sheen.jakma.org> (raw)
In-Reply-To: <7vfylyx3e3.fsf@assigned-by-dhcp.cox.net>
Hi Junio,
On Fri, 3 Mar 2006, Junio C Hamano wrote:
> Recently some people said "I want to tell git that I renamed fileA
> to fileB" on the list and #git channel,
> *1* This is by design, and I am not going to debate if that is a
> good design or not here.
Thanks for your detailed email. Before I continue digesting it, I'd
like to revise my original proposal (having now read the
more of the 'design philosophy'):
- I want to tell git that object A is related to object B between two
trees.
I think at this stage a proof-of-concept would be an idea. I'll try
get back with that before end of the month.
regards,
--
Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A
Fortune:
we just switched to Sprint.
next prev parent reply other threads:[~2006-03-04 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 4:03 On recording renames Junio C Hamano
2006-03-04 4:09 ` Paul Jakma [this message]
2006-03-04 6:16 ` Junio C Hamano
2006-03-04 13:19 ` Junio C Hamano
2006-03-04 17:36 ` Linus Torvalds
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=Pine.LNX.4.64.0603040405260.13612@sheen.jakma.org \
--to=paul@clubi.ie \
--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).