Thread (40 messages) flat view 40 messages, 12 authors, 2016-06-15

Re: What's cooking in git.git (topics)

From: Nicolas Pitre <hidden>
Date: 2016-06-15 22:43:53

Possibly related (same subject, not in this thread)

On Sat, 24 Nov 2007, Jeff King wrote:
On Fri, Nov 23, 2007 at 01:23:44PM +0000, Johannes Schindelin wrote:
quoted
Maybe we could change the (non-fast forward) message into (non-fast 
forward; need to pull?).
Not unreasonable, although I think our line length is getting a bit
long.  Rejected refs would look something like (actually they say
"[rejected]" but the text is column-aligned with the X's):

 ! XXXXXXX...XXXXXXX ref_name -> ref_name (non-fast forward; need to pull?)

There's 58 characters of text not including the two ref_names, leaving
about 11 characters for each ref name. The name of this topic,
jk/send-pack, would overflow an 80-character terminal:

 ! [rejected]        jk/send-pack -> jk/send-pack (non-fast forward; need to pull?)
I personally think this is a bad idea, especially after all the efforts 
that has been put into making those lines not to wrap.

Yet the message itself is not totally accurate either, since "need to 
pull" might have to be "need to force" in some cases.

I think that would be better to append a single line at the end of the 
display with a clue about what "non fast forward" means.


Nicolas
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help