From: "Aaron Gray" <aaronngray.lists@googlemail.com>
To: "Tim Visher" <tim.visher@gmail.com>
Cc: <pascal@obry.net>, "Git Mailing List" <git@vger.kernel.org>
Subject: Re: git svn teething problems - initial clone okay - fetches not working
Date: Mon, 23 Mar 2009 22:49:27 -0000 [thread overview]
Message-ID: <D9560AEA971144C99A0540C08AAFC3D1@HPLAPTOP> (raw)
In-Reply-To: c115fd3c0903231458t7ac8ac69if6b7bdb3a7d8861b@mail.gmail.com
On Mon, Mar 23, 2009 at 5:31 PM, Aaron Gray
<aaronngray.lists@googlemail.com> wrote:
>> Aaron Gray a écrit :
>>>
>>> Anyway I am having the problem that I can do a 'git svn fetch' and I see
>>> changes coming in. But the gitweb and another git clone from it do not
>>> reflect those changes. The repository is still showing its two days old.
>>
>> You need a:
>>
>> $ git svn rebase
>
> I tried that.
>
>> to fetch *and* merge the changes into the local tracking branch (master
>> by default).
>
> Pascal,
>
> Could you give me a full set of instructions for importing :-
>
> http://llvm.org/svn/llvm-project/llvm
>
It sounds like your working directory might be dirty. Are you sure
all of your changes have been committed?
Probably. I am getting an error on doing 'git svn rebase' :-
many filenames * : needs update
update---index --refresh: command returned error: 1
Could you please give me the command to import the above SVN repository so I
can redo the thing from scratch.
Many thanks in advance,
Aaron
next prev parent reply other threads:[~2009-03-23 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 19:30 git svn teething problems - initial clone okay - fetches not working Aaron Gray
2009-03-23 19:43 ` Tim Visher
2009-03-23 20:02 ` Aaron Gray
2009-03-23 21:03 ` Pascal Obry
2009-03-23 21:31 ` Aaron Gray
2009-03-23 21:58 ` Tim Visher
2009-03-23 22:49 ` Aaron Gray [this message]
2009-03-24 6:41 ` Pascal Obry
2009-03-24 11:45 ` Tim Visher
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=D9560AEA971144C99A0540C08AAFC3D1@HPLAPTOP \
--to=aaronngray.lists@googlemail.com \
--cc=git@vger.kernel.org \
--cc=pascal@obry.net \
--cc=tim.visher@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 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).