Re: git-svn: What is --follow-parent / --no-follow-parent for?

[Steven Michalske]

On Nov 19, 2012, at 11:31 PM, Sebastian Leske sebastian.le...@sleske.name 
wrote:
 
 Commit graph of git-svn result:
 
 --follow-parent:   --no-follow-parent:
 
 
   |   |
  /| | |
 / | | |
 | | | |
 | | | |
 | | | |
 \ | | |
  \| | |
   |   | 
 
 
 (please excuse cheap ASCII art)
 
 Is that the only effect of --no-follow-parent? And again, why would I
 want that?

I suppose that you would want this for a SVN repo that holds many different and 
possibly loosely related projects.
The you can apply git filter branch then to split them up cleanly.

e.g. Imagine that the two root commits of the branches do not have true common 
history.

Steve

--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [RFC 1/4 v2] Implement a basic remote helper for svn in C.

[Steven Michalske]

On Jul 2, 2012, at 4:07 AM, Jonathan Nieder jrnie...@gmail.com wrote:

 [...]
 diff: Use fifo instead of pipe: Retrieve the name of the pipe from env and 
 open it
 for svndump.
 
 I'd prefer to avoid this if possible, since it means having to decide
 where the pipe goes on the filesystem.  Can you summarize the
 discussion in the commit message so future readers understand why
 we're doing it?

Crazy thought here but would a socket not be a bad choice here?

Imagine being able to ssh tunnel into the SVN server and run the helper with 
filesystem access to the SVN repo.

Akin to the pushy project use case.
http://packages.python.org/pushy/

SSH into the machine, copy the required components to the machine, and use the 
RPC.
Nothing needed but SSH and python.  In this case SSH, SVN, and the helper would 
be needed.

This also would work just fine with the local host too.

Steve

Note: Resent, Sorry it was signed, and rejected before.--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: bzr-git: keep empty directories

[Steven Michalske]

Perhaps having a file named something like:

.git_foreign_scm_empty_dir  or some shorter name.

With the contents of the fast importer empty directory info put in there; If 
any book keeping is needed.

It also looks like you strip out meta-data.
perhaps a file like:

.git_foreign_scm_metadata

We could use the .git/config file format for storing the bookkeeping data.

Steve

On Jul 14, 2012, at 3:46 PM, David Aguilar wrote:

 On Sat, Jul 14, 2012 at 7:41 AM, Felix Natter fnat...@gmx.net wrote:
 hello,
 
 when converting a repo from bzr to git:
 
 mkdir freeplane-git1
 cd freeplane-git1
 git init .
 bzr fast-export --plain --export-marks=../marks.bzr ../trunk/ | git 
 fast-import --export-marks=../marks.git
 git checkout
 
 Empty directories are not contained in the git working index. This is
 because of the --plain option, which Excludes metadata to maximise
 interoperability and thus does not support empty directories
 (http://doc.bazaar.canonical.com/plugins/en/fastimport-plugin.html).
 
 However, when I use --no-plain (which according to above documentation
 exports empty directories), git cannot handle it:
 
 $ ./freeplane2git.sh
 Initialized empty Git repository in /home/felix/git/freeplane-git1/.git/
 15:56:09 Calculating the revisions to include ...
 15:56:09 Starting export of 4290 revisions ...
 fatal: This version of fast-import does not support feature 
 commit-properties.
 fast-import: dumping crash report to .git/fast_import_crash_3915
 bzr: broken pipe
 
 I already tried to hack bzr-fastimport's exporter.py so that it does not
 emit commit properties but emits empty directories but i was not
 successful.
 
 So is there another way to preserve empty directories or shall I report
 a bug on bzr fast-export?
 
 Many thanks in advance!
 
 I would suggest hacking it to optionally not emit commit properties as step 
 one.
 
 A later enhancement would be to optionally create directories with
 empty .gitignore files, or something similar. git really doesn't care
 about empty directories.
 -- 
 David
 --
 To unsubscribe from this list: send the line unsubscribe git in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html