git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ray Chen <rchen@cs.umd.edu>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Eric Wong <normalperson@yhbt.net>,
	Michael Haggerty <mhagger@alum.mit.edu>,
	git@vger.kernel.org
Subject: Re: [PATCH/RFC] git-svn: New flag to add a file in empty directories
Date: Wed, 18 May 2011 07:10:23 -0400	[thread overview]
Message-ID: <BANLkTinvFKAsh5N92rSH26Y12dV6bPQFUw@mail.gmail.com> (raw)
In-Reply-To: <4DD38DEE.4080604@drmicha.warpmail.net>

On Wed, May 18, 2011 at 5:14 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
>>
>> I strongly believe git-svn should leave no trace.  Nobody but the user
>> using git-svn should know they're using git-svn to interact with an SVN
>> repo.  This allows users to stay under the radar of any idiotic rules
>> (or knee-jerk reactions of FUD) their organization may have against
>> using non-standard SVN clients.  So far, it's worked out pretty well,
>> git-svn users slowly and quietly develop clout and influence to migrate
>> their repos from SVN to git.
>
> git-svn's maintenance of these files would be simpler if we used a
> special file for that, say .git-svn-empty-dir, and teach dcommit to
> ignore it. That way git clones can share it and git svn dcommit is
> unimpaired. The only problem occurs when a new git-svn commits these,
> and old git clones that and an old git-svn dcommits from that clone.
>

I'll let people more experienced than I come to a conclusion on this one.

I can say I'm loath to spend a lot of time on this, given that it
might all be replaced within two months by Dmitry Ivankov's GSoC
project.

- Ray

  reply	other threads:[~2011-05-18 11:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 22:00 [PATCH/RFC] git-svn: New flag to add a file in empty directories Ray Chen
2011-05-18  7:22 ` Michael Haggerty
2011-05-18  8:33   ` Eric Wong
2011-05-18  9:14     ` Michael J Gruber
2011-05-18 11:10       ` Ray Chen [this message]
2011-05-18 10:59     ` Ray Chen
2011-05-18 20:01       ` Eric Wong
2011-05-19  3:11     ` Michael Haggerty
2011-05-18 10:46   ` Ray Chen
2011-05-18  8:22 ` Eric Wong
2014-07-23  0:06 ` Gaffney

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=BANLkTinvFKAsh5N92rSH26Y12dV6bPQFUw@mail.gmail.com \
    --to=rchen@cs.umd.edu \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    --cc=normalperson@yhbt.net \
    /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).