From: tab@snarc.org (Vincent Hanquez)
To: Alex Riesen <raa.lkml@gmail.com>
Cc: "Brandon Casey" <casey@nrlssc.navy.mil>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>,
torvalds@linux-foundation.org, gitster@pobox.com,
mkraai@beckman.com, madcoder@debian.org, git@vger.kernel.org
Subject: Re: [PATCH] Prefer $EMAIL over auto-generated user@hostname.
Date: Fri, 6 Jul 2007 17:59:02 +0200 [thread overview]
Message-ID: <20070706155902.GA17489@snarc.org> (raw)
In-Reply-To: <81b0412b0707060859u6a1c3a24p4399a71d84038615@mail.gmail.com>
On Fri, Jul 06, 2007 at 05:59:19PM +0200, Alex Riesen wrote:
> On 7/6/07, Brandon Casey <casey@nrlssc.navy.mil> wrote:
> >
> >Is the recommended tab stop 8 characters as it is for linux? or 4?
> >
>
> Tab is always 8 spaces. It is indentation which can be 8, 4, 3, 2, and even
> 1.
> It is 8 in Git.
tab isn't 8 spaces. a tab is a tab.
It's usually *APPEARING* at 8 spaces. they *may* appears as a different
size (to fit anyone preferences), as long as they stay as a tab (not
expanded), and that nobody is aligning on tabs.
=> this way the how many spaces should indentation be has no meaning
since everybody can choose it on their own terminal/display without
setting any value across readers of the code.
Cheers,
--
Vincent Hanquez
next prev parent reply other threads:[~2007-07-06 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 15:03 [PATCH] Prefer $EMAIL over auto-generated user@hostname Brandon Casey
2007-07-06 15:11 ` Uwe Kleine-König
2007-07-06 15:22 ` Brandon Casey
2007-07-06 15:32 ` Johannes Schindelin
2007-07-06 15:51 ` Brandon Casey
2007-07-06 15:59 ` Alex Riesen
2007-07-06 15:59 ` Vincent Hanquez [this message]
2007-07-06 16:22 ` Alex Riesen
2007-07-06 16:23 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2007-07-06 16:14 Brandon Casey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070706155902.GA17489@snarc.org \
--to=tab@snarc.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=madcoder@debian.org \
--cc=mkraai@beckman.com \
--cc=raa.lkml@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=ukleinek@informatik.uni-freiburg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).