From: Boaz Harrosh <bharrosh@panasas.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Johannes Sixt <j.sixt@viscovery.net>,
Stephan Beyer <s-beyer@gmx.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Keep committer and committer dates
Date: Thu, 05 Jun 2008 19:34:25 +0300 [thread overview]
Message-ID: <48481591.8090703@panasas.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0806051704311.1798@tm8103-a.perex-int.cz>
Jaroslav Kysela wrote:
> On Thu, 5 Jun 2008, Johannes Schindelin wrote:
>
>> Clearly, you do not want to be convinced, no matter what arguments are
>> thrown your way.
>
> No, I just do not want to be restricted with one way to do things. All
> what I read is about fear to misuse the proposed feature. It stops
> evolution, especially in open source - propose to remove 'rm -rf /' from
> all linux distros. Anyway, GIT maintainer has a right to not accept my
> change, altough I think that it's a drawback for other users - not for me.
> Bye for now.
>
> Jaroslav
>
> -----
> Jaroslav Kysela <perex@perex.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, Red Hat, Inc.
>
Please consider looking at this in another way.
You know how in git the crypto signature of the patch, which is it's
"object name" (OID) that you see in git log, also contains it's parent, though
recursively proving that same OID is exactly, universe wide, the same tree.
and all this stuff about git...
Well consider the "committer" field to be the person how created and signed
that OID. That is, the person that first defined that universe unique tree.
An OID of a patch is not about the patch it's about the tree. And so is the
"committer" field. It's not who wrote the patch, it's about who signed the
tree up to this point.
If you absolutely need to emulate someone else name just do
$ su that_other_one
But don't ask git to record an information that was not true at that
point in time.
My $0.017
Boaz
prev parent reply other threads:[~2008-06-05 16:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 14:59 [PATCH] Keep committer and committer dates Jaroslav Kysela
2008-06-03 20:16 ` Johannes Schindelin
2008-06-04 9:16 ` Jaroslav Kysela
2008-06-04 10:29 ` Karl Hasselström
2008-06-04 11:12 ` Jakub Narebski
2008-06-04 12:29 ` Jaroslav Kysela
2008-06-04 14:22 ` Nicolas Pitre
2008-06-04 15:43 ` Johannes Schindelin
2008-06-05 1:03 ` Stephan Beyer
2008-06-05 4:25 ` Johannes Schindelin
2008-06-05 5:03 ` Junio C Hamano
2008-06-05 7:10 ` Johannes Sixt
2008-06-05 12:44 ` Jaroslav Kysela
2008-06-05 13:13 ` Johannes Schindelin
2008-06-05 13:38 ` Jaroslav Kysela
2008-06-05 13:54 ` Johannes Schindelin
2008-06-05 14:11 ` Jaroslav Kysela
2008-06-05 14:46 ` Johannes Schindelin
2008-06-05 15:16 ` Jaroslav Kysela
2008-06-05 16:34 ` Boaz Harrosh [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=48481591.8090703@panasas.com \
--to=bharrosh@panasas.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=perex@perex.cz \
--cc=s-beyer@gmx.net \
/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).