On 2/24/18 3:36 PM, don fong wrote:
> Eric, thanks for the tip.
>
> my feeling is that regardless of whether these files are pushed, they
> clutter up the "git status" listing after i've done a build.
You don't have to build in the source directory.
--
``The lyf so short, the craft so long to l
Eric, thanks for the tip.
my feeling is that regardless of whether these files are pushed, they
clutter up the "git status" listing after i've done a build.
On Sat, Feb 24, 2018 at 11:28 AM, Eric Blake wrote:
> On 02/24/2018 01:26 PM, Chet Ramey wrote:
>>
>> On 2/24/18 1:46 AM, don fong wrote:
On 02/24/2018 01:26 PM, Chet Ramey wrote:
On 2/24/18 1:46 AM, don fong wrote:
based on my experience creating one patch, running "make" and "make
test", i found that "git status" was reporting a lot of generated and
built files that i think should be ignored.
Those files aren't ever pushed to
On 2/24/18 1:46 AM, don fong wrote:
> based on my experience creating one patch, running "make" and "make
> test", i found that "git status" was reporting a lot of generated and
> built files that i think should be ignored.
Those files aren't ever pushed to the bash git repositories (master,
devel
On 2/23/18 10:20 PM, don fong wrote:
> hi folks. i'm a bash user, who just noticed a slight anomaly. it has
> to with the shell variable modifier ${parameter?} . according to the
> man page, ${X?} should yield an error message and exit if X is unset,
> otherwise the value of X. in this case,
>
