search for: gitigror

...dra <artagnon at gmail.com> wrote: > Add several .gitignore rules to various directories to ensure a clean > worktree after a default build. Hi, These gitignore lists require maintenance. Is is possible to express the same set of filenames as patterns like '*.inc' in the root gitigrore file, so that adding/removing a new generated file does not require updating gitignore? Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/

...ote: >> Add several .gitignore rules to various directories to ensure a clean >> worktree after a default build. > > Hi, > > These gitignore lists require maintenance. Is is possible to express > the same set of filenames as patterns like '*.inc' in the root > gitigrore file, so that adding/removing a new generated file does not > require updating gitignore? That's a valid concern, but there are plenty of *.inc files that aren't meant to be ignored; for example lib/Support/Unix/Host.inc. I can't think of any other patterns that would further simp...

Add several .gitignore rules to various directories to ensure a clean worktree after a default build. Signed-off-by: Ramkumar Ramachandra <artagnon at gmail.com> --- Just cloned and built LLVM. This annoyed me. Here's a trivial patch. .gitignore | 10 ++++++++++ bindings/ocaml/llvm/.gitignore | 1 + docs/.gitignore

...ignore rules to various directories to ensure a clean >>> worktree after a default build. >> >> Hi, >> >> These gitignore lists require maintenance. Is is possible to express >> the same set of filenames as patterns like '*.inc' in the root >> gitigrore file, so that adding/removing a new generated file does not >> require updating gitignore? > > That's a valid concern, but there are plenty of *.inc files that > aren't meant to be ignored; for example lib/Support/Unix/Host.inc. I > can't think of any other patterns...