git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Mathias Waack <Mathias.Waack@rantzau.de>
Cc: git@vger.kernel.org
Subject: Re: Joining Repositories
Date: Wed, 18 Jan 2006 15:14:43 +0100	[thread overview]
Message-ID: <20060118141442.GP28365@pasky.or.cz> (raw)
In-Reply-To: <200601181501.38791.Mathias.Waack@rantzau.de>

  Hello,

Dear diary, on Wed, Jan 18, 2006 at 03:01:38PM CET, I got a letter
where Mathias Waack <Mathias.Waack@rantzau.de> said that...
> On Wednesday 18 January 2006 01:58 pm, Petr Baudis wrote:
> > Dear diary, on Wed, Jan 18, 2006 at 01:51:58PM CET, I got a letter
> > where Petr Baudis <pasky@suse.cz> said that...
> >
> > >   But if you want r1/a, r2/b to turn to r/r1/a, r/r2/b, you will have
> > > to rewrite the history of each (and then do the above). One rough
> > > and untested sketch...
> > >
> > > 	mkdir r1-rewritten
> > > 	cd r1-rewritten
> > > 	cp -a ../r1/.git .
> >
> > 	mkdir commitmap
> >
> > > 	for commit in $(git-rev-list --topo-order HEAD | tac); do
> > > 		git-read-tree --prefix=r1/ $commit
> 
> ...git-read-tree doesn't know the parameter --prefix (just downloaded and 
> tried it on 0.99.9i). What version shall I use?

  oops, it seems this is only in the latest pu branch of git. If you are
not brave enough for that, you will need to use the prefix facility of
checkout-index instead, and it'll take much longer:

	git-read-tree $commit
	git-checkout-index -a --prefix=r1/
	rm .git/index
	cg-add -r r1/
	rm -rf r1
	.. then proceed with git-cat-file etc ..

  Note that I'm not sure when which feature was introduced. Your best
bet is to just use the latest stable GIT/Cogito versions.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Of the 3 great composers Mozart tells us what it's like to be human,
Beethoven tells us what it's like to be Beethoven and Bach tells us
what it's like to be the universe.  -- Douglas Adams

  reply	other threads:[~2006-01-18 14:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 12:25 Joining Repositories Mathias Waack
2006-01-18 12:51 ` Petr Baudis
2006-01-18 12:58   ` Petr Baudis
2006-01-18 14:01     ` Mathias Waack
2006-01-18 14:14       ` Petr Baudis [this message]
2006-01-19 11:36         ` Mathias Waack
2006-01-19 18:24         ` Junio C Hamano
2006-01-18 14:14       ` Andreas Ericsson
2006-01-18 14:09   ` Ryan Anderson
2006-01-18 14:21     ` Petr Baudis
2006-01-18 14:39       ` Ryan Anderson
2006-01-18 16:23     ` Linus Torvalds
2006-01-18 17:05       ` Petr Baudis
2006-01-18 17:33         ` Junio C Hamano
2006-01-18 18:03         ` Linus Torvalds
2006-01-18 17:30       ` Junio C Hamano
2006-01-18 18:22         ` Linus Torvalds
2006-01-18 19:09           ` Junio C Hamano
2006-01-18 20:09             ` Linus Torvalds
2006-01-18 22:47               ` Linus Torvalds
2006-01-18 23:15                 ` Linus Torvalds
2006-01-19  2:12         ` Junio C Hamano
2006-01-19  9:03           ` Petr Baudis
2006-01-18 18:55       ` Ryan Anderson
2006-01-18 16:38 ` H. Peter Anvin

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=20060118141442.GP28365@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=Mathias.Waack@rantzau.de \
    --cc=git@vger.kernel.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).