From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Alex Bennee <kernel-hacker@bennee.com>, git@vger.kernel.org
Subject: Re: Adding Reviewed-by/Tested-by tags to other peoples commits
Date: Sat, 11 Oct 2008 14:18:43 -0700 [thread overview]
Message-ID: <7v7i8ekez0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0810111457300.22125@pacific.mpi-cbg.de.mpi-cbg.de> (Johannes Schindelin's message of "Sat, 11 Oct 2008 15:06:48 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Color me puzzled. You said in another mail that you think this is the
> task for the MUA.
Not really. I said that I think people usually do this in MUA with the
current system. I did not mean to say that I think such a partition of
jobs between commit and MUA is ideal.
>> This is a bit tangent, but perhaps rebase needs a hook so that users can
>> strip certain tags automatically from the commit log messages (e.g.
>> things like Reviewd-by: and Tested-by: become less trustworthy when you
>> rebase; S-o-b: becomes somewhat less trustworthy when you "edit" in
>> rebase-i; etc).
>
> Maybe. I am not really convinced of the S-o-b. You kept stressing that
> the SOB is not about validity, but a statement that the patch is
> intellectually proper or some such (IOW it means something like "Darl,
> forget it"). And the point of origin does not change, even if you rebase
> the commit.
The "somewhat less trustworthy" kicks in when you "edit" in rebase-i if
you change the tree that gets recorded. You are right that it is
irrelevant if you ran rebase-i to only edit the commit log message.
prev parent reply other threads:[~2008-10-11 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 6:37 Adding Reviewed-by/Tested-by tags to other peoples commits Alex Bennee
2008-10-11 7:46 ` Jeff King
2008-10-11 10:58 ` Johannes Schindelin
2008-10-11 11:28 ` Junio C Hamano
2008-10-11 10:42 ` Johannes Schindelin
2008-10-11 11:48 ` Junio C Hamano
2008-10-11 13:06 ` Johannes Schindelin
2008-10-11 21:18 ` Junio C Hamano [this message]
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=7v7i8ekez0.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.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).