git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Sekhar Nori <nsekhar@ti.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/1] git-am: provide configuration to enable signoff by default
Date: Wed, 1 Jun 2011 12:39:19 -0400	[thread overview]
Message-ID: <20110601163919.GC7132@sigill.intra.peff.net> (raw)
In-Reply-To: <1306917751-27999-1-git-send-email-nsekhar@ti.com>

On Wed, Jun 01, 2011 at 02:12:31PM +0530, Sekhar Nori wrote:

> Provide a git config option to enable --signoff a
> default when using git-am. This should be handy
> for maintainers who regularly apply patches from
> mailing lists to send them upstream and want to
> be on the sign-off path.

I think people have complained about auto-signoff features before,
because it was supposed to be a conscious act. I don't recall if it was
ever resolved, and I don't have an opinion myself, but it may be worth
searching the archives for past arguments.

> diff --git a/git-am.sh b/git-am.sh
> index 6cdd591..8e2a693 100755
> --- a/git-am.sh
> +++ b/git-am.sh
> @@ -328,6 +328,11 @@ then
>      keepcr=t
>  fi
>  
> +if test "$(git config --bool --get am.signoff)" = true
> +then
> +    sign=t
> +fi
> +
>  while test $# != 0
>  do
>  	case "$1" in

Shouldn't this be turned off if --rebasing is passed? Otherwise you
would introduce signoffs during rebase (I didn't check, though, so maybe
there is some other mechanism preventing it).

-Peff

  parent reply	other threads:[~2011-06-01 16:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01  8:42 [PATCH 1/1] git-am: provide configuration to enable signoff by default Sekhar Nori
2011-06-01 16:03 ` Sverre Rabbelier
2011-06-02 19:10   ` Nori, Sekhar
2011-06-02 19:41     ` Thiago Farina
2011-06-01 16:39 ` Jeff King [this message]
2011-06-01 17:14 ` Junio C Hamano
2011-06-01 18:27   ` Nori, Sekhar
2011-06-01 19:23     ` Jonathan Nieder
2011-06-02 19:05       ` Nori, Sekhar

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=20110601163919.GC7132@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nsekhar@ti.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.
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).