Vitaliy Margolen wrote:
> Nikolay Sivov wrote:
>
>> Vitaliy Margolen wrote:
>>
>>> Nikolay Sivov wrote:
>>>
>>>
Is there any way not to include a regenerated 'configure' script into
a patch but be able to 'git fetch' it when it's changed remotely in
repo?
A
Nikolay Sivov wrote:
> Vitaliy Margolen wrote:
>> Nikolay Sivov wrote:
>>
>>> Is there any way not to include a regenerated 'configure' script into
>>> a patch but be able to 'git fetch' it when it's changed remotely in
>>> repo?
>>>
>>> As I see there is no need to patch a 'configure' file in re
Vitaliy Margolen wrote:
> Nikolay Sivov wrote:
>
>> Is there any way not to include a regenerated 'configure' script into a
>> patch but be able to 'git fetch' it when it's changed remotely in repo?
>>
>> As I see there is no need to patch a 'configure' file in repository
>> since it's always
Nikolay Sivov wrote:
> Is there any way not to include a regenerated 'configure' script into a
> patch but be able to 'git fetch' it when it's changed remotely in repo?
>
> As I see there is no need to patch a 'configure' file in repository
> since it's always regenerated when 'configure.ac' cha
Is there any way not to include a regenerated 'configure' script into a
patch but be able to 'git fetch' it when it's changed remotely in repo?
As I see there is no need to patch a 'configure' file in repository
since it's always regenerated when 'configure.ac' changed.
Thanks in advance.
