git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wade Berrier" <wberrier@gmail.com>
To: git@vger.kernel.org
Subject: git-svn feature request: exclude certain subpaths on clone
Date: Thu, 4 Dec 2008 09:43:47 -0700	[thread overview]
Message-ID: <bbbeeccd0812040843p3e5547c4tac88b0d01562a37f@mail.gmail.com> (raw)

Hi,

Consider the following example layout:

trunk/src
trunk/big_fat_binary_blobs
trunk/doc

I think it would be really nice to be able to tell git-svn to ignore
'big_fat_binary_blobs' while keeping 'src' and 'doc'.

I know someone is thinking, "Why did you check in
'big_fat_binary_blobs' in the first place?"  In this case, the
repository is out of my control.  For the svn users, it's not that big
of a deal since they only get one HEAD version of the binary_blobs.
But when trying to clone with git-svn, I repeatedly get out of memory
and packing errors (every 1000 commits) when packing several revisions
of these binary_blobs.  (Now, that may be a bug in of itself... which
can reproduced by creating an svn repo with several revisions of
KNOPPIX at the same path, followed by a git svn clone )

Anyway, I still think it may be useful to be able to ignore certain
paths on a clone.  In thinking about the implementation details, I
figure probably the best approach would be to manually purge the
unwanted path after it has been fetched, but before it is committed.
That way, if a commit contains changes in paths that are both wanted
and unwanted, the commit could be 'pruned'.

I've looked at the git-svn script a little, but wanted to solicit
feedback and ideas before continuing further.

Thoughts?

Wade

             reply	other threads:[~2008-12-04 16:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 16:43 Wade Berrier [this message]
2008-12-06  0:13 ` git-svn feature request: exclude certain subpaths on clone 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=bbbeeccd0812040843p3e5547c4tac88b0d01562a37f@mail.gmail.com \
    --to=wberrier@gmail.com \
    --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).