Thread (17 messages) flat view 17 messages, 7 authors, 2016-06-15

Re: [PATCH] defaults for where to merge from (take 3)

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:57

Possibly related (same subject, not in this thread)

"Alex Riesen" [off-list ref] writes:
On 3/1/07, Paolo Bonzini [off-list ref] wrote:
quoted
quoted
Actually, how about making the default configurable _AND_ have
the --no-track option (for scripting)?
Fine by me.  And also --track in case you want to try it out.  ;-)
Ack. Thanks!
Having both --track and --no-track options is a nice touch to
give scripts dependable behaviour.  Well done.
quoted
Patch attached.  --remove-section will go in a separate patch.
Still think it is a very dangerous operation.
I am going to bed now, but I would appreciate if the list could
help Paolo:

 (1) with styles.  I have only given a cursory look at the
     patch, but I think people already know what I like and not
     like.

 (2) by reviewing the changes to the .config writer.  That
     traditionally has been one of the more fragile parts of the
     system, and I am reluctant to look at it.

 (3) come up with a version that is easier-to-apply (including
     sending an in-line patch).

I would just feel better to see a patch like this, which is a
significant improvement to the system, to be properly signed-off
by the submitter.

Also it would be nice if you guys can fight it out about the
default value for 'tracked'.  I do not think _I_ can defend the
position to create these tracking configurations by default to
old timers (especially the ones that do not follow the git
mailing list), as I am not convinced (not yet, anyway).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help