From: martin f krafft <madduck@madduck.net>
To: git discussion list <git@vger.kernel.org>
Subject: git-svn: expand svn:keywords, or how else to deal with them?
Date: Fri, 9 May 2008 11:19:19 +0100 [thread overview]
Message-ID: <20080509101919.GA25037@lapse.madduck.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
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.
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...
--
martin | http://madduck.net/ | http://two.sentenc.es/
"a mathematician is a device for turning coffee into theorems."
-- paul erdös
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-05-09 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 10:19 martin f krafft [this message]
2008-05-11 8:45 ` git-svn: expand svn:keywords, or how else to deal with them? Eric Wong
2008-05-11 10:39 ` martin f krafft
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=20080509101919.GA25037@lapse.madduck.net \
--to=madduck@madduck.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.