Commit is removed upstream. Please do git reset --hard origin/master in
your tree. When on master branch if you have no work on master branch and
git rebase -I origin/master and remove commit manually otherwise
Le 3 nov. 2015 4:59 AM, "Andrei Borzenkov" a écrit :
> 31.10.2015 16:46, Andrei Borzen
31.10.2015 16:46, Andrei Borzenkov пишет:
31.10.2015 10:02, Andreas Schwab пишет:
Kaz Kylheku writes:
Nope. They will have a git in which that commit looks like their own
local work. *Someone* will inadvertently do a "git push" to blast out
their changes based on that deleted commit, thereby
"Lennart Sorensen" writes:
> On Sat, Oct 31, 2015 at 08:24:06AM +0300, Andrei Borzenkov wrote:
>> If we decide to fix this commit it is better done now, while it is the last
>> one. It is annoying but do you have suggestion how it can be done
>> differently?
>
> Well the only options are:
>
> 1)
On 02.11.2015 07:11, Lennart Sorensen wrote:
On Sat, Oct 31, 2015 at 08:24:06AM +0300, Andrei Borzenkov wrote:
If we decide to fix this commit it is better done now, while it is the
last
one. It is annoying but do you have suggestion how it can be done
differently?
Well the only options are:
On Sat, Oct 31, 2015 at 08:24:06AM +0300, Andrei Borzenkov wrote:
> If we decide to fix this commit it is better done now, while it is the last
> one. It is annoying but do you have suggestion how it can be done
> differently?
Well the only options are:
1) Leave it alone
2) Break the tree of anyo
Opened Savannah support ticket
Le 31 oct. 2015 2:54 PM, "Andrei Borzenkov" a écrit :
> 30.10.2015 23:19, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
>
>> On 30.10.2015 21:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>
>>> On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>>
> 30.10.2015 23:59, Lennart Sorensen пишет:
>
>> On Fri, Oct 30, 2015 at 09:19:19PM +0100, Vladimir 'φ-coder/phcoder'
>> Serbinenko wrote:
>>
>>> On 30.10.2015 21:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>>
On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>
30.10.2015 23:19, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
On 30.10.2015 21:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 30.10.2015 15:26, Andrei Borzenkov wrote:
See
http://git.savannah.gnu.org/cgit/grub.git/commit/?
31.10.2015 10:02, Andreas Schwab пишет:
Kaz Kylheku writes:
Nope. They will have a git in which that commit looks like their own
local work. *Someone* will inadvertently do a "git push" to blast out
their changes based on that deleted commit, thereby causing it to
reappear.
Not if another on
Kaz Kylheku writes:
> Nope. They will have a git in which that commit looks like their own
> local work. *Someone* will inadvertently do a "git push" to blast out
> their changes based on that deleted commit, thereby causing it to
> reappear.
Not if another one pushes something different in the
On 30.10.2015 13:59, Lennart Sorensen wrote:
I don't have non-fast-forward rights. Does someone from savannah-users
have them? Could he just delete this commit?
If you do that, then anyone that already did a pull after it went in
will have a broken tree. Rather annoying.
Nope. They will have
30.10.2015 23:59, Lennart Sorensen пишет:
On Fri, Oct 30, 2015 at 09:19:19PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
On 30.10.2015 21:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 30.10.2015 15:26, Andrei Borz
On 30 Oct 2015 9:06 pm, "Vladimir 'φ-coder/phcoder' Serbinenko" <
phco...@gmail.com> wrote:
>
> On 30.10.2015 15:26, Andrei Borzenkov wrote:
> > See
> >
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc319df14cd3398fbdfde665ac
> >
> >
> > I was not even aware that this is possib
On Fri, Oct 30, 2015 at 09:19:19PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
> On 30.10.2015 21:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> > On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> >> On 30.10.2015 15:26, Andrei Borzenkov wrote:
> >>> See
> >>> http://
On 30.10.2015 21:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> On 30.10.2015 15:26, Andrei Borzenkov wrote:
>>> See
>>> http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc319df14cd3398fbdfde665ac
>>>
>>>
>>>
On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 30.10.2015 15:26, Andrei Borzenkov wrote:
>> See
>> http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc319df14cd3398fbdfde665ac
>>
>>
>> I was not even aware that this is possible. Is there anything on server
>
On 30.10.2015 15:26, Andrei Borzenkov wrote:
> See
> http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc319df14cd3398fbdfde665ac
>
>
> I was not even aware that this is possible. Is there anything on server
> side that can prevent it?
>
> Would be good if commit were amended an
On Fri, Oct 30, 2015 at 05:26:00PM +0300, Andrei Borzenkov wrote:
> See
> http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc319df14cd3398fbdfde665ac
>
> I was not even aware that this is possible. Is there anything on server side
> that can prevent it?
I would have thought th
> > See
> > http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc3
> 19df14cd3398fbdfde665ac
> >
> >
> >
> >
> > I was not even aware that this is possible. Is there anything on
> > server side that can prevent it?
> >
> > Would be good if commit were amended and force pushed
On Fri, 30 Oct 2015 17:26:00 +0300
Andrei Borzenkov wrote:
> See
> http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc319df14cd3398fbdfde665ac
>
> I was not even aware that this is possible. Is there anything on
> server side that can prevent it?
A hook running on "update" ev
See
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc319df14cd3398fbdfde665ac
I was not even aware that this is possible. Is there anything on server
side that can prevent it?
Would be good if commit were amended and force pushed to fix it.
___
21 matches
Mail list logo