On Mon, Apr 27, 2015 at 9:45 AM, Emilio G. Cota <c...@braap.org> wrote:
> Signed-off-by: Emilio G. Cota <c...@braap.org>
> ---
> .gitignore | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.gitignore b/.gitignore
> index aed0e1f..025a841 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -62,6 +62,7 @@
> *.fn
> *.ky
> *.log
> +*.patch
This Issue is discussed and I think it was concluded to not gitignore
patches. See:
commit f3a22014e94dfaacb57277dafce66b41cd994869
Author: Michael Tokarev <m...@tls.msk.ru>
Date: Thu Jun 6 01:14:54 2013 +0400
gitignore: unignore *.patch
This partially reverts:
commit 082369e62c5bbaba89f173c2b803bc24115bb111
Author: liguang <lig.f...@cn.fujitsu.com>
Date: Fri Mar 22 16:44:13 2013 +0800
gitignore: ignore more files
I'm not sure how this went in. The thing is that
ignoring *.patch, in my opinion, is just wrong.
Especially for downstreams who apply patches for
real.
Signed-off-by: Michael Tokarev <m...@tls.msk.ru>
Regards,
Peter
> *.pdf
> *.pod
> *.cps
> --
> 1.9.1
>
>
