[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Reproduce-devel] [task #15262] Source code downloads and Job manager

From: Mohammad Akhlaghi
Subject: [Reproduce-devel] [task #15262] Source code downloads and Job manager
Date: Sun, 7 Jul 2019 16:02:26 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0

Follow-up Comment #23, task #15262 (project reproduce):

These have been the conventions we have been using until now (they just
weren't actually written down, but if you run `git log' you'll see them
implemented consistently). 

So if you want to suggest a modification to them, please define a new task and
we can talk about them there.

To see the importance of the 75 character limit, run `git log' and see the
different between your commit message and the rest. The 
standard/default terminal width is 80 characters and Git indents all the lines
of the message (to separate basic commit meta-data like author, date and etc).
So if the lines in your commit message are longer than 75 characters, the
extra characters will go onto the next line and break the visual indentation
(and thus easy identification of the commit message).

If you have the luxury of expanding your terminal (for example on a GUI), then
you can fix it by picking up the mouse and making your terminal emulator
bigger (a HUGE distraction!!!!). But you don't always have that luxury and
your terminal is fixed by hardware to 80 characters (since it has been a
standard for decades).

But anyway, please define a new task for suggestions in new conventions
(including any answer you might have to the points I raised above) ;-).


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]