From: Jeff Brown <jeff@jeffandbetsy.net>
To: git@vger.kernel.org
Subject: Re: problems syncing with svn
Date: Fri, 27 Mar 2009 09:58:43 -0400 [thread overview]
Message-ID: <bbd12f0f0903270658o73e9305dj15903f4c50278952@mail.gmail.com> (raw)
In-Reply-To: <bbd12f0f0903270617m3c2233b2g6c6e8c3d9a9b50a4@mail.gmail.com>
On Fri, Mar 27, 2009 at 9:17 AM, Jeff Brown <jeff@jeffandbetsy.net> wrote:
> I have found numerous folks having a similar problem but have not
> found a solution that works for me. This is what I have:
>
> I have svn clone'd a repo. I have added a git remote to the project.
> I have pulled from the git repo. When I attempt to "svn dcommit", the
> commit fails with...
>
> Unable to extract revision information from commit
> 26c8e90f67d40d9193fe276f3bcbfdd4e9161730~1
>
> What I really want to do is move our primary development support to
> git (github in particular right now). I want to setup a job that will
> periodically grab the latest code from github and push those changes
> to our svn repo. These will be the only commits made to svn.
> Developers will no longer be committing to svn. We need the svn repo
> kept up to date for a few reasons but do not want to do development
> against svn directly.
>
> Any advice would be much appreciated.
>
> Thanks in advance.
>
If repo details will help, the git repo is at
http://github.com/grails/grails/tree/master and the original svn repo
which that came from is at https://svn.codehaus.org/grails/trunk/.
Thanks again.
Jeff
--
Jeff Brown
SpringSource
http://www.springsource.com/
Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/
prev parent reply other threads:[~2009-03-27 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 13:17 problems syncing with svn Jeff Brown
2009-03-27 13:58 ` Jeff Brown [this message]
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=bbd12f0f0903270658o73e9305dj15903f4c50278952@mail.gmail.com \
--to=jeff@jeffandbetsy.net \
--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).