git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Anderson <ryan@michonline.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Mathias Waack <Mathias.Waack@rantzau.de>, git@vger.kernel.org
Subject: Re: Joining Repositories
Date: Wed, 18 Jan 2006 09:39:17 -0500	[thread overview]
Message-ID: <43CE5315.8060008@michonline.com> (raw)
In-Reply-To: <20060118142139.GQ28365@pasky.or.cz>

[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]

Petr Baudis wrote:

>Dear diary, on Wed, Jan 18, 2006 at 03:09:17PM CET, I got a letter
>where Ryan Anderson <ryan@michonline.com> said that...
>  
>
>>... Why would that be the optimal method?
>>
>Ow. I suppose that's what you call "blinded by invalid implicit
>assumptions". Obviously, if you are ok with such a grand move, this is
>the best.
>  
>
Sorry, that came out a bit harsher than I had intended.

>This also reminds me that I should finally merge the cg-mv patch.
>
>>	git fetch ../r1/
>>	GIT_INDEX_FILE=.git/tmp-index git-read-tree FETCH_HEAD
>>	GIT_INDEX_FILE=.git/tmp-index git-checkout-cache -a -u
>>	git-update-cache --add -- $(GIT_INDEX_FILE=.git/tmp-index git-ls-files)
>>	cp .git/FETCH_HEAD .git/MERGE_HEAD
>>	git commit
>>    
>>
>
>But if you want to have an idea what's actually going on on the high
>level, perhaps the
>
>	cd r2
>	cg-branch-add r1 ../r1/.git
>	cg-fetch r1
>	cg-merge -j r1
>
>might be easier. ;-)
>
Ah, yes, cg-merge seems like it might be somewhat simpler here.


-- 

Ryan Anderson
  sometimes Pug Majere


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2006-01-18 14:39 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
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 [this message]
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=43CE5315.8060008@michonline.com \
    --to=ryan@michonline.com \
    --cc=Mathias.Waack@rantzau.de \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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).