<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/git-pull.sh, branch v1.7.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v1.7.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v1.7.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2010-05-25T17:49:54Z</updated>
<entry>
<title>pull: do nothing on --dry-run</title>
<updated>2010-05-25T17:49:54Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2010-05-25T06:07:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=29609e682226acbdaa3340145792b5bd7a1ef5a8'/>
<id>urn:sha1:29609e682226acbdaa3340145792b5bd7a1ef5a8</id>
<content type='text'>
Pull was never meant to take --dry-run at all. However, it
passes unknown arguments to git-fetch, which does do a
dry-run. Unfortunately, pull then attempts to merge whatever
cruft was in FETCH_HEAD (which the dry-run fetch will not
have written to).

Even though we never advertise --dry-run as something that
should work, it is still worth being defensive because:

  1. Other commands (including fetch) take --dry-run, so a
     user might try it.

  2. Rather than simply producing an error, it actually
     changes the repository in totally unexpected ways.

This patch makes "pull --dry-run" equivalent to "fetch
--dry-run".

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'maint'</title>
<updated>2010-03-20T18:29:19Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2010-03-20T18:29:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=96203bb074544a37fcff9c3f2a68582b76caa263'/>
<id>urn:sha1:96203bb074544a37fcff9c3f2a68582b76caa263</id>
<content type='text'>
* maint:
  Update draft release notes to 1.7.0.3
  fetch: Fix minor memory leak
  fetch: Future-proof initialization of a refspec on stack
  fetch: Check for a "^{}" suffix with suffixcmp()
  daemon: parse_host_and_port SIGSEGV if port is specified
  Makefile: Fix CDPATH problem
  pull: replace unnecessary sed invocation
</content>
</entry>
<entry>
<title>pull: replace unnecessary sed invocation</title>
<updated>2010-03-20T14:25:02Z</updated>
<author>
<name>Stephen Boyd</name>
<email>bebarino@gmail.com</email>
</author>
<published>2010-03-18T05:10:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0d12e59f636b68964c80a82a58020d34a6cd5032'/>
<id>urn:sha1:0d12e59f636b68964c80a82a58020d34a6cd5032</id>
<content type='text'>
Getting the shortened branch name is as easy as using the shell's
parameter expansion.

Signed-off-by: Stephen Boyd &lt;bebarino@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>fetch and pull: learn --progress</title>
<updated>2010-02-24T16:35:45Z</updated>
<author>
<name>Tay Ray Chuan</name>
<email>rctay89@gmail.com</email>
</author>
<published>2010-02-24T12:50:28Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=9839018e874d4f15e820e1272f1ac575186c4fdc'/>
<id>urn:sha1:9839018e874d4f15e820e1272f1ac575186c4fdc</id>
<content type='text'>
Note that in the documentation for git-pull, documentation for the
--progress option is displayed under the "Options related to fetching"
subtitle via fetch-options.txt.

Also, update the documentation of the -q/--quiet option for git-pull to
mention its effect on progress reporting during fetching.

Signed-off-by: Tay Ray Chuan &lt;rctay89@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>pull: re-fix command line generation</title>
<updated>2010-01-24T18:11:27Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2010-01-24T18:11:27Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7ecee3314fdafd8015fd14bfb76ae4b601acc25e'/>
<id>urn:sha1:7ecee3314fdafd8015fd14bfb76ae4b601acc25e</id>
<content type='text'>
14e5d40 (pull: Fix parsing of -X&lt;option&gt;, 2010-01-17) forgot that
merge_name needs to stay as a single non-interpolated string.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'ap/merge-backend-opts'</title>
<updated>2010-01-21T04:28:50Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2010-01-21T04:28:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=fcb2a7e4a3c7899a3432f5804889fa3ea5779220'/>
<id>urn:sha1:fcb2a7e4a3c7899a3432f5804889fa3ea5779220</id>
<content type='text'>
* ap/merge-backend-opts:
  Document that merge strategies can now take their own options
  Extend merge-subtree tests to test -Xsubtree=dir.
  Make "subtree" part more orthogonal to the rest of merge-recursive.
  pull: Fix parsing of -X&lt;option&gt;
  Teach git-pull to pass -X&lt;option&gt; to git-merge
  git merge -X&lt;option&gt;
  git-merge-file --ours, --theirs

Conflicts:
	git-compat-util.h
</content>
</entry>
<entry>
<title>pull: Fix parsing of -X&lt;option&gt;</title>
<updated>2010-01-18T06:46:27Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2010-01-18T06:31:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=14e5d40ca4f4f118fe03cbe5302309170b46096d'/>
<id>urn:sha1:14e5d40ca4f4f118fe03cbe5302309170b46096d</id>
<content type='text'>
As -X parameter can contain arbitrary $IFS characters, we need to
properly quote it from the shell while forming the command line.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Teach git-pull to pass -X&lt;option&gt; to git-merge</title>
<updated>2010-01-18T06:45:17Z</updated>
<author>
<name>Avery Pennarun</name>
<email>apenwarr@gmail.com</email>
</author>
<published>2009-11-26T02:23:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ee2c79552acceaa59a78518c6c084bd515606374'/>
<id>urn:sha1:ee2c79552acceaa59a78518c6c084bd515606374</id>
<content type='text'>
This needs the usual sq then eval trick to allow IFS characters
in the option.

Signed-off-by: Avery Pennarun &lt;apenwarr@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Be more user-friendly when refusing to do something because of conflict.</title>
<updated>2010-01-12T21:17:08Z</updated>
<author>
<name>Matthieu Moy</name>
<email>Matthieu.Moy@imag.fr</email>
</author>
<published>2010-01-12T09:54:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d38a30df7dd54c5c6883af1de1a03ec7d523cee5'/>
<id>urn:sha1:d38a30df7dd54c5c6883af1de1a03ec7d523cee5</id>
<content type='text'>
Various commands refuse to run in the presence of conflicts (commit,
merge, pull, cherry-pick/revert). They all used to provide rough, and
inconsistant error messages.

A new variable advice.resolveconflict is introduced, and allows more
verbose messages, pointing the user to the appropriate solution.

For commit, the error message used to look like this:

$ git commit
foo.txt: needs merge
foo.txt: unmerged (c34a92682e0394bc0d6f4d4a67a8e2d32395c169)
foo.txt: unmerged (3afcd75de8de0bb5076942fcb17446be50451030)
foo.txt: unmerged (c9785d77b76dfe4fb038bf927ee518f6ae45ede4)
error: Error building trees

The "need merge" line is given by refresh_cache. We add the IN_PORCELAIN
option to make the output more consistant with the other porcelain
commands, and catch the error in return, to stop with a clean error
message. The next lines were displayed by a call to cache_tree_update(),
which is not reached anymore if we noticed the conflict.

The new output looks like:

U       foo.txt
fatal: 'commit' is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm &lt;file&gt;' as
appropriate to mark resolution and make a commit, or use 'git commit -a'.

Pull is slightly modified to abort immediately if $GIT_DIR/MERGE_HEAD
exists instead of waiting for merge to complain.

The behavior of merge and the test-case are slightly modified to reflect
the usual flow: start with conflicts, fix them, and afterwards get rid of
MERGE_HEAD, with different error messages at each stage.

Signed-off-by: Matthieu Moy &lt;Matthieu.Moy@imag.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'maint'</title>
<updated>2009-12-09T06:47:09Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2009-12-09T06:47:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ff86bdd5cac70850eea4791bea78efa19b228ebe'/>
<id>urn:sha1:ff86bdd5cac70850eea4791bea78efa19b228ebe</id>
<content type='text'>
* maint:
  add-interactive: fix deletion of non-empty files
  pull: clarify advice for the unconfigured error case
</content>
</entry>
</feed>
