From: Benoit Sigoure <tsuna@lrde.epita.fr>
To: git@vger.kernel.org
Cc: normalperson@yhbt.net
Subject: [PATCH 0/5] Add easy access to SVN properties in git-svn.
Date: Mon, 15 Oct 2007 17:34:45 +0200 [thread overview]
Message-ID: <1192462485-3730-1-git-send-email-tsuna@lrde.epita.fr> (raw)
Hello,
this is a fairly simple patch series that adds easy access to SVN properties
from within git-svn.
The first patch simply factors some code that was used for
git-svn show-ignore in order to easily implement git-svn create-ignore (2nd
patch). The 3rd and 4th patch implement git-svn propget / proplist to easily
access SVN properties. The last patch does some cleanup because I found it
more convenient to not have to remember to add a `\n' at the end of each
error message.
git-svn.perl | 201 +++++++++++++++++++++++++++++++++++++---------
t/t9101-git-svn-props.sh | 72 ++++++++++++++++-
2 files changed, 233 insertions(+), 40 deletions(-)
reply other threads:[~2007-10-16 14:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1192462485-3730-1-git-send-email-tsuna@lrde.epita.fr \
--to=tsuna@lrde.epita.fr \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).