From: Mihamina Rakotomandimby <mihamina@gulfsat.mg>
To: git list <git@vger.kernel.org>
Subject: use case, advices (SVN/GIT)
Date: Thu, 22 Apr 2010 15:14:01 +0300 [thread overview]
Message-ID: <20100422151401.2c47aa76@pbmiha.malagasy.com> (raw)
Manao ahoana, Hello, Bonjour,
We'd rather use GIT.
But there is a project, that we regularily pull (Coova:
http://coova.org/CoovaChilli/Developers) which is under SVN.
I first "svn export" this project.
I initiate a new GIT repository based on what I "exported".
I make my changes, and commit them.
I month (and several commits) later, I would like to sync with Coova
SVN.
It's a one way "pull": I wont push my changes to their repository.
What's your recommended way to handle this?
Misaotra, Thanks, Merci.
--
Architecte Informatique chez Blueline/Gulfsat:
Administration Systeme, Recherche & Developpement
+261 34 29 155 34 / +261 33 11 207 36
next reply other threads:[~2010-04-22 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 12:14 Mihamina Rakotomandimby [this message]
2010-04-23 15:25 ` use case, advices (SVN/GIT) Ulrich Spörlein
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=20100422151401.2c47aa76@pbmiha.malagasy.com \
--to=mihamina@gulfsat.mg \
--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).