git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thiago Farina <tfransosi@gmail.com>
To: David Fraser <davidf@sjsoft.com>
Cc: git@vger.kernel.org, David Moore <davidm@sjsoft.com>
Subject: Re: [PATCH] Initial manually svn property setting support for git-svn
Date: Wed, 16 Sep 2009 13:18:50 -0300	[thread overview]
Message-ID: <a4c8a6d00909160918r77e418dbpe8debeff58d595c9@mail.gmail.com> (raw)
In-Reply-To: <1927112650.1281253084529659.JavaMail.root@klofta.sjsoft.com>

On Wed, Sep 16, 2009 at 4:02 AM, David Fraser <davidf@sjsoft.com> wrote:
> This basically stores an attribute 'svn-properties' for each file that needs them changed, and then sets the properties when committing.
>
> Issues remaining:
>  * The way it edits the .gitattributes file is suboptimal - it just appends to the end the latest version
>  * It could use the existing code to get the current svn properties to see if properties need to be changed; but this doesn't work on add
>  * It would be better to cache all the svn properties locally - this could be done automatically in .gitattributes but I'm not sure everyone would want this, etc
>  * No support for deleting properties
>
> Usage is:
>  git svn propset PROPNAME PROPVALUE PATH
>
> Added minimal documentation for git-svn propset
>
> Signed-off-by: David Fraser <davidf@sjsoft.com>
> ---
>  Documentation/git-svn.txt |    5 ++
>  git-svn.perl              |   95 ++++++++++++++++++++++++++++++++++++++++++++-
>  2 files changed, 99 insertions(+), 1 deletions(-)
>
David, please read this, line 28:
http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/SubmittingPatches;h=76fc84d8780762e083cd4ca584b9d783b8c0cd81;hb=HEAD

Patches need to be send as plain text, not attached.

  reply	other threads:[~2009-09-16 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1482075216.1261253084509966.JavaMail.root@klofta.sjsoft.com>
2009-09-16  7:02 ` [PATCH] Initial manually svn property setting support for git-svn David Fraser
2009-09-16 16:18   ` Thiago Farina [this message]
2009-09-23  8:58   ` 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=a4c8a6d00909160918r77e418dbpe8debeff58d595c9@mail.gmail.com \
    --to=tfransosi@gmail.com \
    --cc=davidf@sjsoft.com \
    --cc=davidm@sjsoft.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).