Tom Chiverton <tom.chiverton@halliwells.com> wrote on 07/05/2006 08:40:29
AM:
> On Wednesday 05 July 2006 13:36, Mark Phippard wrote:
> > I will not add wrapping because then you cannot control the format of
the
> > message and it messes things up for people using svn log.
>
> I'm not sure why that should be the case- is this because the box can't
tell
> you which are hard (user done) and which are soft (done so it wraps
nicely)
> returns or something ?
Suppose you write a "paragraph" worth of text using wrapping. When we get
the text the soft-wraps all disappear and we will commit with a log
message that is just 1000 characters of text with no breaks in it. When
someone then runs svn log, that is what they get back. If everyone uses a
GUI, it is usually not a problem because the GUI will just soft wrap
again. But if you have any tools utilities that care about the log
message, it really fouls things up.
I just think work wrapping makes it too easy for users to not know they
are doing this, and I am also following the lead of other SVN clients like
TortoiseSVN where this issue has been raised in the past.
> > You can add a
> > property named tsvn:logwidthmarker to your project and we will draw a
line
> > in the box so that you know where to add your hard wraps.
>
> Hmm, well, that's one way of doing it, but I'll have to remember to add
that
> to all the folders/files in a project ?
If you care about seeing that line, then yes. It has to exist on some
parent folder in your workspace. In typical Eclipse development, this
would just be the project folder since you know all users will have that
checked out. The line was mainly added for really anal projects (like
Subversion) where they have a hard rule that no log message have any line
that exceeds n characters.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Jul 5 14:48:22 2006