From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Seth Falcon <sethfalcon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: remotes/* for "foreign" archives
Date: 21 Nov 2006 08:53:17 -0800 [thread overview]
Message-ID: <86lkm4kagy.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <m2y7q4bzo7.fsf@ziti.local>
>>>>> "Seth" == Seth Falcon <sethfalcon@gmail.com> writes:
Seth> This sort of integration could be quite cool. But I think the most
Seth> common use of git-svn is with rebase and not pull. My experience
Seth> with git-svn and pull is that I very quickly ended up making broken
Seth> commits to svn --- I've had much better luck rebasing.
Well, you'd still be using "git-fetch origin" then, transparently,
and your push command could do your preferred thing.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
next prev parent reply other threads:[~2006-11-21 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 17:18 tracking many cvs/svn/git remote archives Randal L. Schwartz
2006-11-21 14:57 ` remotes/* for "foreign" archives (was Re: tracking many cvs/svn/git remote archives) Randal L. Schwartz
2006-11-21 15:13 ` remotes/* for "foreign" archives Seth Falcon
2006-11-21 16:53 ` Randal L. Schwartz [this message]
2006-11-21 19:33 ` Junio C Hamano
2006-11-21 20:42 ` Petr Baudis
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=86lkm4kagy.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=sethfalcon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.