From: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Alex Riesen <raa.lkml@gmail.com>
Subject: Re: Question about handling of heterogeneous repositories
Date: Wed, 30 Nov 2005 15:40:34 +0100 [thread overview]
Message-ID: <200511301540.34776.Josef.Weidendorfer@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0511301457040.2284@wbgn013.biozentrum.uni-wuerzburg.de>
On Wednesday 30 November 2005 14:58, Johannes Schindelin wrote:
> Hi,
>
> On Wed, 30 Nov 2005, Alex Riesen wrote:
>
> > On 11/30/05, Josef Weidendorfer <Josef.Weidendorfer@gmx.de> wrote:
> > >
> > > To detect inter-repository renaming, one has to see both repositories.
> > > Currently, git/cogito etc. commands only work with one repository
> > > only.
> >
> > This case is somewhat special: one is _guaranteed_ to see both
> > repositories.
>
> It is even more so: it is guaranteed that git cannot reconstruct this
> as a move operation.
Say it in another way: because currently, git commands only work in the
scope of one repository, there is no need to want to detect an
inter-repository rename.
Git has no explicit support for renaming, but can do it. Why should it
be a problem to write a tool which is able to detect inter-repository
renames? Still, such a search probably would be very expensive.
git-mv could support this. Additional to deleting from
one repository and adding to the new, it could generate a remark for
the commit message, like:
Added file xxx is from remote repo '/path/myrepo' with name 'yyy'
(file SHA1: 123445... from remote commit SHA1: 345667...)
This info could be interesting both for humans and a history browsing tool.
The tool still would have to know where to look for repo '/path/myrepo'.
It could also work for moving subdirectories (ie. trees instead of files).
Josef
next prev parent reply other threads:[~2005-11-30 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 16:50 Question about handling of heterogeneous repositories Alex Riesen
2005-11-22 19:40 ` Andreas Ericsson
2005-11-22 23:22 ` Alex Riesen
2005-11-27 13:11 ` Petr Baudis
2005-11-29 20:47 ` Alex Riesen
[not found] ` <200511301405.19541.Josef.Weidendorfer@gmx.de>
2005-11-30 13:15 ` Alex Riesen
2005-11-30 13:58 ` Johannes Schindelin
2005-11-30 14:40 ` Josef Weidendorfer [this message]
2005-11-30 15:01 ` Alex Riesen
2005-11-30 16:49 ` Josef Weidendorfer
2005-12-01 8:16 ` Alex Riesen
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=200511301540.34776.Josef.Weidendorfer@gmx.de \
--to=josef.weidendorfer@gmx.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
/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).