From: "David Kågedal" <davidk@lysator•liu.se>
To: git@vger•kernel.org
Subject: Re: [1/2 PATCH] git-svn: make multi-init less confusing
Date: Mon, 08 Jan 2007 14:11:21 +0100 [thread overview]
Message-ID: <877ivxr7d2.fsf@morpheus.local> (raw)
In-Reply-To: 87hcv1r7xv.fsf@morpheus.local
David Kågedal <davidk@lysator•liu.se> writes:
> Seth Falcon <sethfalcon@gmail•com> writes:
>
>> David Kågedal <davidk@lysator•liu.se> writes:
>>> Now if you could only clarify the documentation of dcommit to explain
>>> whether it creates one svn revision per commit in your branch, or if
>>> it creates a single svn revision with the full diff, and the
>>> documentation would be perfect :-)
>>
>> dcommit creates one svn rev for each commit listed by:
>>
>> git log remotes/git-svn..HEAD
>
> So if I want to commit a different subset, is that possible? In my
> case, I have a "master" branch with a few changes on top of git-svn
> that I never want to commit to svn. So what I want is to commit
> "master..HEAD". Can I do that with dcommit? It seems that "git svn
> set-tree master..HEAD" might do the trick.
I tried set-tree now, and all I got was a perl crash:
morpheus% git svn set-tree master..
diff-tree 8dba2b29df78184fef96bbbf9521387846b140b3 b5561ab7309e9b7b3acfacaa786358e7d90665c6
A .gitignore
... more files
Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/SVN/Core.pm line 579.
Malformed file: at /usr/local/bin/git-svn line 459
This is git f4bf2184ae8b79f95b9f56c1ea5455d04e559299 from Jan 1.
Perl is v5.8.8 (Ubunty edgy)
--
David Kågedal
next prev parent reply other threads:[~2007-01-08 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 17:34 git-svn usability David Kågedal
2007-01-05 2:02 ` [1/2 PATCH] git-svn: make multi-init less confusing Eric Wong
2007-01-05 6:37 ` David Kågedal
2007-01-05 15:38 ` Seth Falcon
2007-01-08 12:56 ` David Kågedal
2007-01-08 12:58 ` David Kågedal
2007-01-08 13:11 ` David Kågedal [this message]
2007-01-05 2:04 ` [PATCH 2/2] git-svn: update documentation for multi-{init|fetch} Eric Wong
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=877ivxr7d2.fsf@morpheus.local \
--to=davidk@lysator$(echo .)liu.se \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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