On Sun, 15 Feb 2009, Junio C Hamano wrote:
Thanks.
* git-push to update the checked out branch will be refused by default
Make "git push" into a repository to update the branch that is checked
out fail by default.
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
If I understand this one, it will cause grief for quite a few people.
I have a public repository that I push to and then have a trigger that
checks out the current version, compiles it, publishes the compiled
version, sends an announcement, etc
if I am understanding the purpose of this change, you would prohibit the
update from taking place.
the message in the thread that you link to discusses how you want to be
careful about the change, but I have to hunt around through the rest of
the thread to figure out what the change really means (and I'm not sure I
really figured it out)
* git-send-email won't make deep threads by default
Many people said that by default when sending more than 2 patches the
threading git-send-email makes by default is hard to read, and they
prefer the default be one cover letter and each patch as a direct
follow-up to the cover letter.
http://article.gmane.org/gmane.comp.version-control.git/109790
I have mixed feelings about this one, if some messages get delayed in
transit the deep threads still keeps them in order, while the 2-layer
option doesn't.
that being said, I don't think it's that significant to change the
default.
one thing that would help new users is if there was a way to create a git
config file that explicitly listed all the defaults. either as a sample
config, or to expand the existing config file with all the defaults
listed, but commented out.
I find that having such a config file helps me find config options I never
thought to look for.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
