From: Peter Harris <git@peter.is-a-geek.org>
To: John Tapsell <johnflux@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: git svn messages
Date: Tue, 25 Aug 2009 18:49:33 -0400 [thread overview]
Message-ID: <eaa105840908251549o6d53fe9fnb1dfc00395ad36f4@mail.gmail.com> (raw)
In-Reply-To: <43d8ce650908251531n397ba6e1xe71e80d7b8a08344@mail.gmail.com>
On Tue, Aug 25, 2009 at 6:31 PM, John Tapsell wrote:
> Hi all,
>
> When doing git svn dcommit, the messages that it gives are, well,
> frightening :-)
Some moreso than others, depending on your level of familiarity with git. :-)
> It's full of things like:
>
>> No changes between current HEAD and refs/remotes/git-svn
>
> No changes? What's gone wrong? Why can't it find any changes?..
Because you aren't working from a branch-point older than your current
refs/remotes/git-svn. I suppose one could misinterpret that as a
bidirectional "no changes". Still, the message doesn't contain a scary
prefix like "Error:" or even "Warning:". It's just informational.
>> Resetting to the latest refs/remotes/git-svn
>
> That doesn't sound good. Why did it have reset?
Because the newly created svn commits are a different DAG from your
former DAG (which contained git commits that weren't in svn yet), even
though the tree contents are the same. The way git-svn tells the rest
of git about this change is by running the "git reset" command.
You can run "gitk" before you run "git svn dcommit", then hit refresh
(F5, I believe) after "git svn dcommit" is done to get a more visual
idea of what is going on.
Peter Harris
prev parent reply other threads:[~2009-08-25 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 22:31 git svn messages John Tapsell
2009-08-25 22:49 ` Peter Harris [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=eaa105840908251549o6d53fe9fnb1dfc00395ad36f4@mail.gmail.com \
--to=git@peter.is-a-geek.org \
--cc=git@vger.kernel.org \
--cc=johnflux@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).