From: Junio C Hamano <junkio@cox.net>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] Implement git-quiltimport
Date: Tue, 16 May 2006 12:01:27 -0700 [thread overview]
Message-ID: <7vbqtxaj5k.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <m1bqtx6el6.fsf@ebiederm.dsl.xmission.com> (Eric W. Biederman's message of "Tue, 16 May 2006 11:53:41 -0600")
ebiederm@xmission.com (Eric W. Biederman) writes:
> Given the ugliness in -mm making it an error to have an
> non-attributed patch would result in people specifying --author
> when they really don't know who the author is, giving us much
> less reliable information.
>
> Possibly what we need is an option to not make it an error so that
> people doing this kind of thing in their own trees have useful
> information.
I agree it is probably a good way to error by default, optinally
allowing to say "don't care". I do not think Linus would pull
from such a tree or trees branched from it into his official
tree, so I do not think we would need to worry about commits
with incomplete information propagating for this particular
"gitified mm" usage. But as a general purpose tool to produce
"gitified quilt series" tree, we would.
It depends on the expected use of the resulting gitified mm
tree.
If it is for an individual developer to futz with and tweak
upon, and the end result from the work leaves such a "gitified
quilt series" repository only as a patch form, then not having
to figure out and specify authorship information to many patches
is probably a plus; the information will not be part of the
official history recorded elsewhere anyway.
However, if it is to produce a reference git tree to point
people at, (i.e. the quiltimport script is run once per a series
by somebody and the result is published for public use), I would
imagine we would want to have the attribution straight, so if
the tool has to "guess", it should either error out or go
interactive and ask.
next prev parent reply other threads:[~2006-05-16 19:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 16:51 [PATCH] Implement git-quiltimport Eric W. Biederman
2006-05-16 17:03 ` Linus Torvalds
2006-05-16 17:53 ` Eric W. Biederman
2006-05-16 19:01 ` Junio C Hamano [this message]
2006-05-17 5:17 ` Eric W. Biederman
2006-05-17 5:31 ` Junio C Hamano
2006-05-17 18:44 ` [PATCH] Implement git-quiltimport (take 2) Eric W. Biederman
2006-05-17 18:51 ` Junio C Hamano
2006-05-17 19:20 ` Eric W. Biederman
2006-05-17 23:34 ` Junio C Hamano
2006-05-18 10:48 ` Eric W. Biederman
2006-05-19 23:58 ` Greg KH
2006-05-20 2:42 ` Eric W. Biederman
2006-05-20 21:32 ` Greg KH
2006-05-21 0:36 ` Eric W. Biederman
2006-05-21 0:41 ` Junio C Hamano
2006-05-21 0:59 ` Eric W. Biederman
2006-05-21 1:02 ` Junio C Hamano
2006-05-21 1:16 ` Eric W. Biederman
2006-06-01 19:23 ` Greg KH
2006-06-02 0:24 ` Eric W. Biederman
2006-05-19 9:55 ` Eric W. Biederman
2006-05-17 20:10 ` [PATCH] Implement a --dry-run option to git-quiltimport Eric W. Biederman
2006-05-17 14:28 ` [PATCH] Implement git-quiltimport Linus Torvalds
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=7vbqtxaj5k.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=ebiederm@xmission.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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).