Re: git-commit-script, was Re: "git revert" (Re: pci_update_resource() getting called on sparc64)

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: git-commit-script, was Re: "git revert" (Re: pci_update_resource() getting called on sparc64)

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

Johannes Schindelin [off-list ref] writes:
And could we rename the *-m* flag at the same time? Because I often catch 
myself typing

	git commit -m "Some_commit_message"
Sure, what's the alternative spelling for the current -m,
though?  Would -c be OK for commit?

Re: git-commit-script, was Re: "git revert" (Re: pci_update_resource() getting called on sparc64)

From: Linus Torvalds <torvalds@osdl.org>
Date: 2016-06-15 22:42:03


On Mon, 8 Aug 2005, Junio C Hamano wrote:
Sure, what's the alternative spelling for the current -m,
though?  Would -c be OK for commit?
How about using long names?

	git commit --reuse-message <sha1>

looks a lot more intuitively understandable to me than something like "-c"

Most of us don't use 300bps terminals any more, so typing a few extra 
characters is probably ok.

Now, to make things be backwards-compatible, it should be easy enough to 
notice

   "Oh, the argument to '-m' is just a single SHA1, let's see if it's a
    commit, and turn '-m' into '--reuse-message' automatically"

If anybody cares. Does cogito already use "-m"?

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