From: Luke Diamand <luke@diamand.org>
To: git@vger.kernel.org
Cc: Pete Wyckoff <pw@padd.com>, Junio C Hamano <gitster@pobox.com>,
Luke Diamand <luke@diamand.org>
Subject: Re: [PATCH] git-p4: warn if git authorship won't be retained
Date: Tue, 10 May 2011 23:11:39 +0100 [thread overview]
Message-ID: <BANLkTi=hi6cZkZAAhJXM04tOk-16x78wYA@mail.gmail.com> (raw)
In-Reply-To: <1305055653-5133-2-git-send-email-luke@diamand.org>
On Tue, May 10, 2011 at 8:27 PM, Luke Diamand <luke@diamand.org> wrote:
> If the git commits you are submitting contain changes made by
> other people, the authorship will not be retained. Change git-p4
> to warn of this and to note that --preserve-user can be used
> to solve the problem (if you have suitable permissions).
> The warning can be disabled.
>
Of course, I've forgotten the && in the test case.
Sigh.
next prev parent reply other threads:[~2011-05-10 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 19:27 [PATCH/RFC v3] git-p4: warn if git authorship won't be retained Luke Diamand
2011-05-10 19:27 ` [PATCH] " Luke Diamand
2011-05-10 22:11 ` Luke Diamand [this message]
2011-05-10 22:51 ` Junio C Hamano
2011-05-11 7:50 ` Luke Diamand
2011-05-10 23:38 ` 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='BANLkTi=hi6cZkZAAhJXM04tOk-16x78wYA@mail.gmail.com' \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pw@padd.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).