git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: schachtobi <schachtobi@web.de>
To: git@vger.kernel.org
Subject: svn propset
Date: Wed, 15 Sep 2010 20:52:25 +0200	[thread overview]
Message-ID: <4C9115E9.4080900@web.de> (raw)

In response to Ramana,

you talked about the svn:ignore property and suggested to have a special
command to set this property. But I think first it could be done
automatically using the semantics git allready has and second there are
other properties that could be treated the same way:

* svn:mime-type
* svn:ignore
* svn:keywords (is there something like this in git?)
* svn:externals (not yet supported? Found nothing so far)
  except solutions here:
http://panthersoftware.com/articles/view/3/svn-s-svn-externals-to-git-s-submodule-for-rails-plugins
  but this is not the same since the client has to setup the links,
repositories etc. And they do not come automatically as in subversion.
  I guess submodules is the proper replacement. But still having the
svn:externals from a pull this could be done automatically without the
need for scripting. And the dcommit should also work for the submodules.
* svn:bugtraq*
* svn:mergeinfo

for me the svn:merginfo and the svn:externals would be most benifitial
since our team uses this a lot and without being able to set those from
git it will be not possible for me to use git for a svn client to do the
merges.

So are there plans or updates to the problems I have encountered?

Thanks!

regards,
Tobias

             reply	other threads:[~2010-09-15 18:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 18:52 schachtobi [this message]
2010-09-29  8:12 ` svn propset - focus on svn:externals Andreas Stricker
  -- strict thread matches above, loose matches on Subject: below --
2010-09-15  1:00 svn propset Ramana Kumar

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=4C9115E9.4080900@web.de \
    --to=schachtobi@web.de \
    --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).