git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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 19:54:32 +0530	[thread overview]
Message-ID: <CAFZEwPNGz18uyLT62PsR-ybF32KJPb5PssQXJXuA4eWUFtPXnw@mail.gmail.com> (raw)
In-Reply-To: <81a197e2-7e0e-176a-c934-0e5f95cfda83@freebsd.org>

Hey Alfred,

On Mon, Jun 13, 2016 at 6:22 PM, Alfred Perlstein <alfred@freebsd.org> wrote:
> Thank you Pranit.  I thought that "signed off by" is used once someone
> approved my patch as opposed to when it's in "proposal" stage.  This was my
> first email with a patch for this issue, who should/could I have used for
> "signoff"?

Signoff is used to indicate that you are OKAY with releasing your
patch according to git's license. For more details see the
Documentation/SubmittingPatches[1]. To summarize you will have to add
this in the end :

   Signed-off-by: Alfred Perlstein <alfred@freebsd.org>

Though I will still recommend you to go through [1] properly.

Regards,
Pranit Bauva

  reply	other threads:[~2016-06-13 14:24 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
2016-06-13 12:52   ` Alfred Perlstein
2016-06-13 14:24     ` Pranit Bauva [this message]
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=CAFZEwPNGz18uyLT62PsR-ybF32KJPb5PssQXJXuA4eWUFtPXnw@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).