[vtk-developers] git branch with missing gerrit change-id

David Gobbi david.gobbi at gmail.com
Wed Jan 22 15:24:57 EST 2014


To amend a whole bunch of commits, use "rebase -i".

rebase -i <branch point>

Within the rebase, change "pick" to "edit" for each of
your commits.

  David


On Wed, Jan 22, 2014 at 1:18 PM, Robert Maynard
<robert.maynard at kitware.com> wrote:
> You can just amend the commit to get a change id.
>
> git commit --amend
>
>
> On Wed, Jan 22, 2014 at 3:02 PM, Sean McBride <sean at rogue-research.com>
> wrote:
>>
>> Hi all,
>>
>> I have a git branch where somehow (it's old, perhaps it predates me
>> running the setup-for-development script?) I have a few commits that lack
>> the gerrit change-id, and so I can't get it into gerrit for review.  How to
>> fix this?  How can I generate a change-id and modify the commit comment to
>> include it?
>>
>> Thanks,
>>
>> --
>> ____________________________________________________________
>> Sean McBride, B. Eng                 sean at rogue-research.com
>> Rogue Research                        www.rogue-research.com
>> Mac Software Developer              Montréal, Québec, Canada
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>



More information about the vtk-developers mailing list