On Wed, May 26, 2010 at 9:00 PM, Robert Haas wrote:
> On Wed, May 26, 2010 at 8:20 PM, Andrew Dunstan
> wrote:
> > Gurjeet Singh wrote:
> >>
> >> I did a `git clean -f -d` and even that did not remove gram.c,
> apparently
> >> because this file _was_ alive at some point in the past hence git won
On Wed, May 26, 2010 at 8:20 PM, Andrew Dunstan wrote:
> Gurjeet Singh wrote:
>>
>> I did a `git clean -f -d` and even that did not remove gram.c, apparently
>> because this file _was_ alive at some point in the past hence git won't
>> remove it even though the current branch does not have gram.c.
Gurjeet Singh wrote:
I did a `git clean -f -d` and even that did not remove gram.c,
apparently because this file _was_ alive at some point in the past
hence git won't remove it even though the current branch does not have
gram.c.
At first glance that looks like a git bug.
cheers
andr
Gurjeet Singh writes:
> The src/backend/parser/gram.c is a generated file, so shouldn't this be
> removed by `make distclean`, or maybe even by `make clean`?
No. It's shipped in distribution tarballs. If you want all derived
files to be removed, use make maintainer-clean.
The src/backend/parser/gram.c is a generated file, so shouldn't this be
removed by `make distclean`, or maybe even by `make clean`?
I did a `git clean -f -d` and even that did not remove gram.c, apparently
because this file _was_ alive at some point in the past hence git won't
remove it even thoug
