From: Strainu <strainu10@gmail.com>
To: Jerry Xinyu Zhao <xyzjerry@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
"openstack-infra@lists.openstack.org"
<openstack-infra@lists.openstack.org>, git <git@vger.kernel.org>
Subject: Re: [OpenStack-Infra] BUG: [Cosmetic] Commiting a gerrit ChangeId before the commit hook was installed
Date: Sat, 18 Jan 2014 01:38:27 +0200 [thread overview]
Message-ID: <CAC9meR+zViFN5PEZxvYp_4XY28OvcR9SeiOP_5DbBCmChYPONg@mail.gmail.com> (raw)
In-Reply-To: <CAE3ttVgs=F2bWbx5qa=dp1kNzgc5djtB3r+2Qp6tvYv-iZKoCw@mail.gmail.com>
Perhaps I haven't been clear enough: the commit already had a change
ID, added manually, so with or without the hook it would have been
attached to the correct review.
In this case, the hook will actually do nothing, making the current
wording of the message confusing IMO. My suggestion was [1] to change
the mesage to "Amending the commit to add a gerrit change id if none
is available." or something similar.
Strainu
[1] https://bugs.launchpad.net/git-review/+bug/1270301
2014/1/18 Jerry Xinyu Zhao <xyzjerry@gmail.com>:
> I think if you hadn't installed the commit hook for generating change ID,
> the commit indeed wouldn't have included a change ID, which is necessary for
> referencing the change when you submit a patch over it. There is nothing
> wrong with the message. git review tool will install the hook and add a
> change ID for you automatically(a new feature of recent git-review release).
>
>
>
> On Fri, Jan 17, 2014 at 1:10 PM, Strainu <strainu10@gmail.com> wrote:
>>
>> 2014/1/17 Jonathan Nieder <jrnieder@gmail.com>:
>> > Hi,
>> >
>> > Strainu wrote:
>> >
>> >> strainu@emily:~/core> git review -f
>> >> Creating a git remote called "gerrit" that maps to:
>> >> ssh://strainu@gerrit.wikimedia.org:29418/pywikibot/core.git
>> >> Your change was committed before the commit hook was installed.
>> >> Amending the commit to add a gerrit change id.
>> >>
>> >> At this point I ended the transaction, as I was confused by the last
>> >> message: I was afraid the ChangeId would have changed, causing the
>> >> patch to be attached to another review.
>> >>
>> >> I think git should not show this message if the change description
>> >> already has a change id
>> >
>> > This message doesn't come from git. It comes from the git-review
>> > tool (in git_review/cmd.py), so cc-ing the authors in case they
>> > have thoughts on that.
>>
>> Thanks for clarifying that. I'll log a bug on launchpad then.
>>
>> Strainu
>>
>> _______________________________________________
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
>
prev parent reply other threads:[~2014-01-17 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 20:23 BUG: [Cosmetic] Commiting a gerrit ChangeId before the commit hook was installed Strainu
2014-01-17 20:41 ` Jonathan Nieder
2014-01-17 21:10 ` Strainu
[not found] ` <CAC9meR+78_EvoqHNcuPyDKOZDjSsUngziGDa2aV1QDtOb8eOXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-17 23:24 ` Jerry Xinyu Zhao
2014-01-17 23:38 ` Strainu [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=CAC9meR+zViFN5PEZxvYp_4XY28OvcR9SeiOP_5DbBCmChYPONg@mail.gmail.com \
--to=strainu10@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=openstack-infra@lists.openstack.org \
--cc=xyzjerry@gmail.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).