Re: [PATCH] Add *.rej to .gitignore

[Sam Ravnborg <sam@ravnborg.org>]

> > From: Jeremy Fitzhardinge <jeremy@goop.org>
> > Date: Tue, 17 Feb 2009 11:59:37 -0800
> > 
> > > *.rej files really are unwanted.  If there are any .rej files, they can be found by
> > > some other means (perhaps git itself could warn when committing with *.rej files present,
> > > or add some distinct notion of "ignored files" vs "never commit" files).
> > > 
> > > (This effectively reverts 1f5d3a6b6532e25a5cdf1f311956b2b03d343a48)
> > > 
> > > Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > 
> > I don't know about this.
> > 
> > I really want to know if there are reject files there if I am 
> > checking to see if my tree is clean.
> > 
> > This has caught many patch application errors for myself 
> > personally in the past, so I really don't want git to start 
> > silently ignoring those things.
> > 
> > People should delete reject file explicitly, as they are 
> > evidence of a patch that would not apply cleanly.  If you 
> > abort trying to add the patch, fine, but cleaning up the 
> > reject files is part of that operation.
> 
> Well, it depends on the workflow. You are making the assumption 
> that everyone is using your workflow, and you are judging them 
> based on that false assumption.
> 
> In my workflow i never miss .rej files because i use tools that 
> _do not allow_ rejects to occur - only if i intentionally force 
> them. So i cannot "miss" any .rej files - i generate them very 
> consciously so all my attention is on them already.
So in your advanced usage it does not matter what git does
with .rej files.
And it hepls people using git in a more naive way.

This is an easy judgement - lets do what benefit the most.

	Sam