Front page

[PATCH] extend gitignore

b54ff7b128594150bac6caa38b045a30
SCORECARD DOCUMENT VIRUS

From: RĂ©mi Rampin <remirampin@gmail.com>
Date: Sun, 28 Aug 2016 11:45:33 -0400

   Indeed, if you won't accept patches with .pyc files in it, putting that in
   the .gitignore file makes a lot of sense.
   
   Clutter is not really an issue if the file is already there... that also
   makes it harder for users to just add that, since then the file will always
   be reported as changed, unless they agree to alter their global settings
   instead for this one project.
   
   On Aug 28, 2016 11:40 AM, "Maximilian Gaukler" <development@maxgaukler.de>
   wrote:
   
   > I don't get your point about why you don't want to include it. From what
   > you say, I understood that you also want a clean `git diff`.
   >
   > As obnam already has a .gitignore, I don't see any downsides of just
   > adding it to make new developers' life easier, as nothing will change for
   > you.
   >
   > From the perspective of someone starting development, having to manually
   > add entries to global a .gitignore is tedious and may even cause problems
   > somewhere else. Actually, the purpose I see in a per-repository .gitignore
   > is that one can just clone and be happy, which is the standard I
   > experienced with almost any significant open-source project.
   >
   > This request was not directed towards other projects, at least as long as
   > I am not working on them :-)
   >
   > Thanks for your consideration,
   >
   > Max
   >
   > _______________________________________________
   > obnam-dev mailing list
   > obnam-dev@obnam.org
   > http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ob
   > nam-dev-obnam.org
   >
From: Maximilian Gaukler <development@maxgaukler.de>
Date: Sun, 28 Aug 2016 15:14:46 +0200

   Hi,
   
   After running `./check`, `git diff` should be empty.
   Please consider the attached patch to fix this.
   
   Thanks,
   
   Max
From: Lars Wirzenius <liw@liw.fi>
Date: Sun, 28 Aug 2016 16:05:36 +0100

   On Sun, Aug 28, 2016 at 03:14:46PM +0200, Maximilian Gaukler wrote:
   > After running `./check`, `git diff` should be empty.
   
   I'm afraid I disagree. I prefer to not put common ones such as *.pyc
   in the per-project .gitignore (I have a lot of Python projects, and I
   don't want to set up a .gitignore for each). I prefer those who want
   them to put the patterns in their global git ignore file. Sorry.
From: Maximilian Gaukler <development@maxgaukler.de>
Date: Sun, 28 Aug 2016 17:41:17 +0200

   I don't get your point about why you don't want to include it. From what 
   you say, I understood that you also want a clean `git diff`.
   
   As obnam already has a .gitignore, I don't see any downsides of just 
   adding it to make new developers' life easier, as nothing will change 
   for you.
   
    From the perspective of someone starting development, having to 
   manually add entries to global a .gitignore is tedious and may even 
   cause problems somewhere else. Actually, the purpose I see in a 
   per-repository .gitignore is that one can just clone and be happy, which 
   is the standard I experienced with almost any significant open-source 
   project.
   
   This request was not directed towards other projects, at least as long 
   as I am not working on them :-)
   
   Thanks for your consideration,
   
   Max
   
   _______________________________________________
   obnam-dev mailing list
   obnam-dev@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org
From: Lars Wirzenius <liw@liw.fi>
Date: Sun, 28 Aug 2016 20:02:51 +0100

   On Sun, Aug 28, 2016 at 05:41:17PM +0200, Maximilian Gaukler wrote:
   > I don't get your point about why you don't want to include it. From what you
   > say, I understood that you also want a clean `git diff`.
   
   I don't find a clean "git status" to be particularly important,
   actually. I'd be happy to remove .gitignore entirely.