Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Katsumi Yamaoka's CVS update of gnus/lisp (73 files)
Date: Fri, 22 Feb 2002 10:04:32 +0100	[thread overview]
Message-ID: <rjg03tvqe7.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <yosu3czu6xh6.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 22 Feb 2002 11:50:45 +0900")

I think it is ok to assume that tab-width is 8 for Gnus, that
assumption is everywhere in the Emacs code. 

On the other hand, I don't think it is worth saving a few bytes to
change existing spaces to tabs, when it doesn't affect indentation.
The price of potential merge conflicts is too high.  You can of course
safely convert spaces to tabs when you modify the code, since that
will lead to not additional conflicts.

On the gripping hand, Katsumi Yamaoka's should not be undone, as that
would just lead to even more conflicts.

In short: set tab-width to 8, and don't worry about space/tabs
otherwise. 




  reply	other threads:[~2002-02-22  9:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21  3:53 Benjamin Rutt
2002-02-21  4:28 ` Katsumi Yamaoka
2002-02-21  4:28 ` Katsumi Yamaoka
2002-02-21 14:04   ` Benjamin Rutt
2002-02-21 14:04   ` Benjamin Rutt
2002-02-21 17:27     ` Kai Großjohann
2002-02-21 17:27     ` Kai Großjohann
2002-02-21 23:47     ` Katsumi Yamaoka
2002-02-21 23:47     ` Katsumi Yamaoka
2002-02-22  0:04       ` Paul Jarc
2002-02-22  0:04       ` Paul Jarc
2002-02-22  1:18       ` Benjamin Rutt
2002-02-22  1:18       ` Benjamin Rutt
2002-02-22  2:50         ` Katsumi Yamaoka
2002-02-22  2:50         ` Katsumi Yamaoka
2002-02-22  9:04           ` Per Abrahamsen [this message]
2003-01-02  2:37           ` Lars Magne Ingebrigtsen
2002-02-21 23:48     ` Paul Jarc
2002-02-21 23:48     ` Paul Jarc
2002-02-21 23:47   ` Paul Jarc
2002-02-22  0:04     ` Katsumi Yamaoka
2002-02-22  0:04     ` Katsumi Yamaoka
2002-02-21 23:47   ` Paul Jarc
  -- strict thread matches above, loose matches on Subject: below --
2002-02-21  3:53 Benjamin Rutt

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=rjg03tvqe7.fsf@ssv2.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).