git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <bebarino@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Theodore Tso <tytso@mit.edu>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] format-patch: Add a signature option (--signature)
Date: Wed, 16 Jun 2010 12:43:50 -0700	[thread overview]
Message-ID: <AANLkTikM8fRb7oeeMrsEfqTzDAYhTJxN63mblhyUXJM6@mail.gmail.com> (raw)
In-Reply-To: <7vwrtygbq5.fsf@alter.siamese.dyndns.org>

On Wed, Jun 16, 2010 at 9:53 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Theodore Tso <tytso@MIT.EDU> writes:
>
>>
>> I don't know how important people will feel this to be, but I've occasionally
>> found it interesting to see how many people are using various different
>> versions of git in a particular development community, and having the
>> version in the signature is a useful gauge on that.
>
> The original motivation of the version signature was exactly that ;-).
>

At least with git send-email you get the X-Mailer header and you know
what version is being used. I admit that isn't as visible/useful as
the signature though and not everyone is using git send-email.

>
> I think you misread Stephen, he misspoke, or I misread the patch.  The
> intention of the change as I understand it is to put the signature in the
> cover letter, in addition to the patches.
>

Yes, this is one intention. The other intention is to allow me to
customize what that signature is (or to have no signature at all).
Currently it replaces the version number.

The other option is appending the signature to the version number, but
I thought it looked funny:

    --
    1.7.0

    Signature goes here

but now that I look at it again maybe it looks ok.

If the answer is there should always be the version number in the
signature then renaming --signature to --custom-signature or
--extra-signature or --append-signature would be more clear (albeit
verbose). Then  --no-*-signature wouldn't imply that you are removing
the default version signature (because you can't).

If the signature is causing problems for third-party tools then maybe
in some projects they wouldn't want the signature at all and
--no-signature would be a good option there. It doesn't mean we have
to add a --signature=<str> option too, instead it could just be a
boolean option.

The real question is how useful is it to have the version number
there? There are other ways to gauge the version usage and it's opt-in
so you'll still get some version number coverage.

  reply	other threads:[~2010-06-16 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15  5:00 [PATCH 1/2] format-patch: Add a signature option (--signature) Stephen Boyd
2010-06-15  5:00 ` [PATCH 2/2] completion: Add --signoff and format.signoff Stephen Boyd
2010-06-15 17:05 ` [PATCH 1/2] format-patch: Add a signature option (--signature) Junio C Hamano
2010-06-16  4:31   ` Stephen Boyd
2010-06-16  5:59 ` [PATCHv2 " Stephen Boyd
2010-06-16  5:59 ` [PATCHv2 2/2] completion: Add --signature and format.signature Stephen Boyd
2010-06-16 13:13 ` [PATCH 1/2] format-patch: Add a signature option (--signature) Theodore Tso
2010-06-16 16:53   ` Junio C Hamano
2010-06-16 19:43     ` Stephen Boyd [this message]
2010-06-16 20:55       ` Junio C Hamano

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=AANLkTikM8fRb7oeeMrsEfqTzDAYhTJxN63mblhyUXJM6@mail.gmail.com \
    --to=bebarino@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tytso@mit.edu \
    /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).