Hi Jan,
Jan Iversen píše v Čt 05. 01. 2017 v 11:50 +0100:
> > Tested this yesterday evening and git commit --amend
> > (Murphy-)worked. IIRC, I committed a patch and tried to change the
> > author later. Don't remember what the exact problem was but in the
>> end only JanIV was able to help me.
> On 5 Jan 2017, at 11:30, Heiko Tietze wrote:
>
> Tested this yesterday evening and git commit --amend (Murphy-)worked. IIRC, I
> committed a patch and tried to change the author later. Don't remember what
> the exact problem was but in the end only JanIV was
Tested this yesterday evening and git commit --amend (Murphy-)worked. IIRC, I
committed a patch and tried to change the author later. Don't remember what the
exact problem was but in the end only JanIV was able to help me.
On 01/04/2017 04:17 PM, Eike Rathke wrote:
> Hi Heiko,
>
> On
Hi Heiko,
On Wednesday, 2017-01-04 15:53:21 +0100, Heiko Tietze wrote:
> Even with 'commit' it doesn't :-)
And what exactly doesn't work?
After
git commit --amend --author='Full Name '
git log HEAD^..
the Author field is shown as ...?
Eike
--
LibreOffice Calc
Hi Heiko,
Heiko Tietze píše v St 04. 01. 2017 v 15:53 +0100:
> > As for me I cannot change the author of a patch (git --amend
--author)
> >
> > I doubt that. This should work:
> >
> > git commit --amend --author='Full Name '
> Even with 'commit' it doesn't :-)
What "it does
Even with 'commit' it doesn't :-)
2017-01-04 15:48 GMT+01:00 Eike Rathke :
> Hi Heiko,
>
> On Wednesday, 2017-01-04 08:47:45 +0100, Heiko Tietze wrote:
>
>> As for me I cannot change the author of a patch (git --amend --author)
>
> I doubt that. This should work:
>
> git commit
Hi Heiko,
On Wednesday, 2017-01-04 08:47:45 +0100, Heiko Tietze wrote:
> As for me I cannot change the author of a patch (git --amend --author)
I doubt that. This should work:
git commit --amend --author='Full Name '
Eike
--
LibreOffice Calc developer. Number formatter
Hi Moggi,
Markus Mohrhard píše v St 04. 01. 2017 v 02:47 +0100:
>
> And in general - what's the reason for such a restriction?
> Why somebody
> cannot eg. backport somebody else's patch to a stable branch,
> even if
> they don't have full commit
2017-01-04 3:28 GMT+01:00 Bjoern Michaelsen :
> If cherrypicking was a free lunch, we could release from master and spare us
> the whole hassle with branches and tags. It isnt.
As for me I cannot change the author of a patch (git --amend --author)
but cherrypick
Hi,
On Tue, Jan 03, 2017 at 10:27:30AM +0100, Jan Holesovsky wrote:
> I wonder - what setting needs to be set for them so that they can push
> other people patches? Or do they need to get the full push rights?
They need the right to "forge commits" as that is what that is.
> And in general -
Hey Kendy,
On Tue, Jan 3, 2017 at 10:27 AM, Jan Holesovsky wrote:
> Hi,
>
> I've heard already from 2 people that it is not possible for them to
> push other people's patches to gerrit; they get an error like:
>
> remote: ERROR: In commit X
Hi,
On Tue, Jan 03, 2017 at 06:14:10PM +0100, Jan Iversen wrote:
> That would call for a third name field in git, right now Git knows Committer
> and Author…what you want is something like Committer, Author, Pusher (sorry
> for the name).
Of course, there is no such thing as a "Pusher". There is
> I've heard already from 2 people that it is not possible for them to
> push other people's patches to gerrit; they get an error like:
>
> remote: ERROR: In commit X
> remote: ERROR: author email address y...@yyy.org
> remote: ERROR: does not match your user
Hi,
I've heard already from 2 people that it is not possible for them to
push other people's patches to gerrit; they get an error like:
remote: ERROR: In commit X
remote: ERROR: author email address y...@yyy.org
remote: ERROR: does not match your user account.
14 matches
Mail list logo