From: "Peter Harris" <git@peter.is-a-geek.org>
To: "Avery Pennarun" <apenwarr@gmail.com>
Cc: gnuruandstuff@yahoo.co.uk, git@vger.kernel.org
Subject: Re: git-svn and svn properties on upstream
Date: Sat, 12 Jul 2008 20:07:36 -0400 [thread overview]
Message-ID: <eaa105840807121707s45dfe936m94a0ceeac82d8a66@mail.gmail.com> (raw)
In-Reply-To: <32541b130807121430ia85a3c8u3efc0b5a8591eb44@mail.gmail.com>
On Sat, Jul 12, 2008 at 5:30 PM, Avery Pennarun wrote:
>
> I guess in an ideal world there'd be a way to track svn properties in
> the git history, but I have no idea where such things should probably
> go.
.gitattributes?
svn:eol-style translates roughly into crlf. svn:keywords translates
(partially) into ident.
git appears to ignore unrecognized entries in .gitattributes. The rest
can be stored there untranslated (or lightly translated - ':' is not
legal for .gitattributes names, if I read the comments correctly).
Peter Harris
prev parent reply other threads:[~2008-07-13 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 19:58 git-svn and svn properties on upstream Paul Talacko
2008-07-12 21:30 ` Avery Pennarun
2008-07-13 0:07 ` Peter Harris [this message]
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=eaa105840807121707s45dfe936m94a0ceeac82d8a66@mail.gmail.com \
--to=git@peter.is-a-geek.org \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gnuruandstuff@yahoo.co.uk \
/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).