On 02/06/2015 02:13 PM, Eric Blake wrote:
> Chet,
>
> I've noticed that your 'devel' branch in bash.git is rather messy;
> basically lots of commits that snapshot the state of a directory, then a
> followup commit that removes leftovers and stray files. If you were to
> set your .gitignore file (
On 02/09/2015 08:19 AM, Chet Ramey wrote:
> On 2/6/15 4:13 PM, Eric Blake wrote:
>> Chet,
>
>> I've noticed that your 'devel' branch in bash.git is rather messy;
>> basically lots of commits that snapshot the state of a directory, then
>> a followup commit that removes leftovers and stray files.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/6/15 4:13 PM, Eric Blake wrote:
> Chet,
>
> I've noticed that your 'devel' branch in bash.git is rather messy;
> basically lots of commits that snapshot the state of a directory, then
> a followup commit that removes leftovers and stray files.
On 06/02/15 21:13, Eric Blake wrote:
> Chet,
>
> I've noticed that your 'devel' branch in bash.git is rather messy;
> basically lots of commits that snapshot the state of a directory, then a
> followup commit that removes leftovers and stray files. If you were to
> set your .gitignore file (to ma
Chet,
I've noticed that your 'devel' branch in bash.git is rather messy;
basically lots of commits that snapshot the state of a directory, then a
followup commit that removes leftovers and stray files. If you were to
set your .gitignore file (to make your exclusion list public) or your
.git/info/
