Re: git-svn: expand svn:keywords, or how else to deal with them?

From: Eric Wong <normalperson@yhbt.net>
Date: May 11, 2008, 08:45 UTC
Message-ID: <20080511084558.GC23929@untitled>
In-Reply-To: <20080509101919.GA25037@lapse.madduck.net>

martin f krafft <madduck@madduck.net> wrote:

Show 16 quoted lines

> Hi,
> 
> I am using git-svn to track an upstream SVN project, which I then
> package for Debian. Upstream uses $Id:$ all over the source code,
> but I am not ready to argue with him that this ought to be removed.
> 
> The problem is that I build the Debian packages out of the git-svn
> tree, but use the published tarball. The latter has $Id:$ expanded
> in all files, while the git-svn tree does not - git-svn does not
> expand them.
> 
> The result is that my Debianisation diff now reverts the expansion
> for every single file. This is quite ugly.
> 
> I realise there are ways to prevent this, but I think that the
> cleanest would be if git-svn could be taught to expand svn:keywords.

*shudder*

> Is this something you could live with, Eric? I am willing to have
> a go at the patch, but my Perl-foo is crap, so I may well fail...

I'll accept a patch for it only if it's optional :) Just the thought of having to do keyword (un)expansion in git-svn is scary; so I'm not willing to do it myself.

I'm mainly uncomfortable with how it'll interact with dcommit usage, but since your use case seems to be fetch-only; you may just disable dcommit if keyword expansion is enabled if it's too painful to figure out the unexpansion...

-- 
Eric Wong