# Perforce Public Depot Jobs
#
#  Job:           The job name. 'new' generates a sequenced job number.
#  Status:        Job status; [open/closed/suspended].  Required
#  Project:       The project this job is for [none/cdsp4/jam/p4hl]  Optional.
#  Severity:      [A/B/C] (A is highest)  Required.
#  ReportedBy     The user who created the job. Can be changed.
#  ReportedDate:  The date the job was created.  Automatic.
#  ModifiedBy:    The user who last modified this job. Automatic.
#  ModifiedDate:  The date this job was last modified. Automatic.
#  OwnedBy:       The owner, responsible for doing the job. Optional.
#  Description:   Description of the job.  Required.
#  DevNotes:      Developer's comments.  Optional.

Job:	job000011

Status:	suspended

Project:	jam

Severity:	C

ReportedBy:	david_abrahams

ReportedDate:	2002/02/25 16:59:14

ModifiedBy:	shawn_hladky

ModifiedDate:	2008/04/13 13:00:54

Description:
	Remove all tabs from Jam sources?
	
	This suggested by David Abrahams in email of 
	
	  BTW, if you want to encourage contribution from the outside,
	  one very simple thing you could do which would help a lot is
	  convert all of your tabs to spaces. Source code formatted
	  with tabs doesn't travel well ;-)
	
	I believe that he may have a good point, and it's usually easy for
	a user's editor to handle tabbing.

DevNotes:
	(rmg)
	Expanding tabs to spaces in a parent branch will create
	regions of merge conflict wherever a file in a child branch
	(branched before the expansion in the parent) has changes.
	
	Are there merge tools that can ignore tab-vs-space
	differences? (I'll look; seems like it should be possible,
	sort of a "merge based on diff -w" thing... [But I note that
	diff3 on my Linux host doesn't seem to know how to do this]).
	
	(rmg)
	Bill Ritcher (Mr. Guiffy) says Guiffy will do this, and 4.0
	with even finer grained "ignore" control.
	
	(rmg)
	Plan is now to do this for the first release after Perforce 2002.2 has
	hit the streets.