git/Documentation/git-push.txt, branch v1.4.2Mirror of https://git.kernel.org/pub/scm/git/git.git/
https://git.shady.money/git/atom?h=v1.4.22006-08-02T18:30:42Zgit-push: allow -f as an alias for --force2006-08-02T18:30:42ZJeff Kingpeff@peff.net2006-08-02T15:28:16Zurn:sha1:8f615493e6b6fd47bc4011c264cb7e6f01052d37
This was already documented in the options section of the manpage. This
patch implements it, adds it to the usage message, and mentions it at the
top of the manpage.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Assorted typo fixes2006-07-09T09:42:41ZPavel Roskinproski@gnu.org2006-07-09T07:44:30Zurn:sha1:addf88e455f85bc6cfe0284b70aaad10b6d3486e
Signed-off-by: Junio C Hamano <junkio@cox.net>
Remove trailing dot after short description2006-03-09T19:44:11ZFredrik Kuivinenfreku045@student.liu.se2006-03-09T16:24:50Zurn:sha1:7bd7f2804d84258a5cd1e76c610496f6beaa4cdf
Signed-off-by: Fredrik Kuivinen <freku045@student.liu.se>
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-push: Update documentation to describe the no-refspec behavior.2006-02-22T06:11:50ZCarl Worthcworth@cworth.org2006-02-22T04:28:50Zurn:sha1:aa064743fa69e2806d5e0af1fab103baa6fa57cd
It turns out that the git-push documentation didn't describe what it
would do when not given a refspec, (not on the command line, nor in a
remotes file). This is fairly important for the user who is trying to
understand operations such as:
git clone git://something/some/where
# hack, hack, hack
git push origin
I tracked the mystery behavior down to git-send-pack and lifted the
relevant portion of its documentation up to git-push, (namely that all
refs existing both locally and remotely are updated).
Signed-off-by: Carl Worth <cworth@cworth.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Docs: minor git-push copyediting2006-02-07T05:14:57ZJ. Bruce Fieldsbfields@fieldses.org2006-02-06T00:42:27Zurn:sha1:cc55aaec38ddebd2e6f69fc3895cec393a61956e
Minor git-push copyediting
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Docs: move git url and remotes text to separate sections2006-02-07T05:14:56ZJ. Bruce Fieldsbfields@fieldses.org2006-02-05T23:29:49Zurn:sha1:85a97d4e10c1ac4b87e856e2efe7bcd53d6868c3
The sections on git urls and remotes files in the git-fetch,
git-pull, and git-push manpages seem long enough to be worth a
manpage section of their own.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Docs: split up pull-fetch-param.txt2006-02-07T05:14:55ZJ. Bruce Fieldsbfields@fieldses.org2006-02-05T22:43:47Zurn:sha1:3598a308086d4a41cab1e941df7763f2004e53c5
The push and pull man pages include a bunch of shared text from
pull-fetch-param.txt. This simplifies maintenance somewhat, but
there's actually quite a bit of text that applies only to one or the
other.
So, separate out the push- and pull/fetch-specific text into
pull-fetch-param.txt and git-push.txt, then include the largest chunk
of common stuff (the description of protocols and url's) from
urls.txt. That cuts some irrelevant stuff from the man pages without
making us duplicate too much.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Merge fixes up to GIT 1.1.62006-01-30T01:56:45ZJunio C Hamanojunkio@cox.net2006-01-30T01:56:45Zurn:sha1:36b5b3c65948694d9a92de5a17f2b97c3cd84879git push -f documentation2006-01-30T01:54:43ZJ. Bruce Fieldsbfields@fieldses.org2006-01-30T01:40:50Zurn:sha1:f0fff36e82bc8cc12be58a0585106ee720c4dc98
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-push: fix --tags and document it.2006-01-16T07:59:12ZJunio C Hamanojunkio@cox.net2006-01-16T07:27:34Zurn:sha1:42301e34a2736b091738d4ca6a23fd90bd1f1837
Previously 'git-push --tags dst', used information from
remotes/dst to determine which refs to push; this patch corrects
it, and also documents the --tags option.
Signed-off-by: Junio C Hamano <junkio@cox.net>