On Fri, Jan 04, 2008 at 11:13:14PM +0100, Andi Kleen wrote:
> On Friday 04 January 2008 19:47:33 Joe Perches wrote:
> > On Fri, 2008-01-04 at 19:06 +0100, Andi Kleen wrote:
> > > But the problem with your "rule" is that every of the hundreds
> > > of Linux kernel contributors will need to do the same. And that's just
> > > ineffecient, waste of valuable human work and just doesn't make much
> > > sense.
> > >
> > > It certainly won't improve Linux in any way.
> >
> > What I would prefer is a git option that supports
> > check-in/outs in a coding style of a user choice.
>
> I'm not very deep into git specifics, but for the spaces<->tab problem
> I suspect some kind of commit hook script would be the correct solution.
> i.e. always convert them in newly changed lines as comitted.
If you've got the very latest git, after
cd linux-2.6/
echo "* whitespace" >.gitattributes
it'll treat any spaces in initial whitespace that could have been tabs
as bad whitespace, for the purposes of commands like git-am. (So e.g.
git-am --whitespace=fix mbox
will rewrite such stuff with tabs.) For details search for whitespace
in the gitattributes, git-config, and git-apply man pages....
--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
