From: Pranit Bauva <pranit.bauva@gmail.com>
To: Alfred Perlstein <alfred@freebsd.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Git List <git@vger.kernel.org>, Eric Wong <e@80x24.org>,
Joseph Pecoraro <pecoraro@apple.com>,
David Fraser <davidf@sjsoft.com>
Subject: Re: [PATCH] Document the 'svn propset' command.
Date: Mon, 13 Jun 2016 12:29:08 +0530 [thread overview]
Message-ID: <CAFZEwPM5qnzw7RCUwOkJFo+U982kVGU8_3GUTXvHAypKtvEgTQ@mail.gmail.com> (raw)
In-Reply-To: <20160612191550.GA14160@elvis.mu.org>
Hey Alfred,
On Mon, Jun 13, 2016 at 12:45 AM, Alfred Perlstein <alfred@freebsd.org> wrote:
> Junio + all,
>
> A week ago I was requested to provide documentation for the
> 'svn propset' command. I have attached a diff off of the
> 'maint' branch for this, however it seems to apply cleanly
> to 'master' as well.
>
> Thank you for your patience.
>
> This is also available on my github here:
> https://github.com/splbio/git/tree/document_propset
I am not particularly sure whether the above could form a good commit
message. I think you wanted to include this as a comment. git-am picks
up these patches. The title commit is taken from the subject stripping
the '[PATCH]'. Then the body before '---' is taken as the rest of the
commit message. Then the diff is applied. To include comments add them
after ---. Also please have a look at Documentation/SubmittingPatches.
Also missing signoff. For the patch to actually be accept you need to
follow those instructions. Thanks for contributing.
> ---
> Documentation/git-svn.txt | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
> index fb23a98..e104824 100644
> --- a/Documentation/git-svn.txt
> +++ b/Documentation/git-svn.txt
> @@ -459,6 +459,20 @@ Any other arguments are passed directly to 'git log'
> Gets the Subversion property given as the first argument, for a
> file. A specific revision can be specified with -r/--revision.
>
> +'propset'::
> + Sets the Subversion property given as the first argument, to the
> + value given as the second argument for the file given as the
> + third argument.
> ++
> +Example:
> ++
> +------------------------------------------------------------------------
> +git svn propset svn:keywords "FreeBSD=%H" devel/py-tipper/Makefile
> +------------------------------------------------------------------------
> ++
> +This will set the property 'svn:keywords' to 'FreeBSD=%H' for the file
> +'devel/py-tipper/Makefile'.
> +
> 'show-externals'::
> Shows the Subversion externals. Use -r/--revision to specify a
> specific revision.
Regards,
Pranit Bauva
next prev parent reply other threads:[~2016-06-13 6:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 19:15 [PATCH] Document the 'svn propset' command Alfred Perlstein
2016-06-13 6:59 ` Pranit Bauva [this message]
2016-06-13 12:52 ` Alfred Perlstein
2016-06-13 14:24 ` Pranit Bauva
2016-06-13 14:42 ` Pranit Bauva
2016-06-13 22:09 ` Alfred Perlstein
2016-06-15 5:19 ` Alfred Perlstein
2016-06-15 20:15 ` Eric Wong
2016-06-15 20:21 ` Junio C Hamano
2016-06-15 20:24 ` Alfred Perlstein
2016-06-15 20:32 ` Joseph Pecoraro
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFZEwPM5qnzw7RCUwOkJFo+U982kVGU8_3GUTXvHAypKtvEgTQ@mail.gmail.com \
--to=pranit.bauva@gmail.com \
--cc=alfred@freebsd.org \
--cc=davidf@sjsoft.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pecoraro@apple.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).