<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/git.git/git-pull.sh, branch v1.5.4.4</title>
<subtitle>Git
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.5.4.4</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.5.4.4'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/'/>
<updated>2008-01-27T02:24:24Z</updated>
<entry>
<title>pull --rebase: be cleverer with rebased upstream branches</title>
<updated>2008-01-27T02:24:24Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>Johannes.Schindelin@gmx.de</email>
</author>
<published>2008-01-26T18:04:37Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=c85c79279df2c8a583d95449d1029baba41f8660'/>
<id>urn:sha1:c85c79279df2c8a583d95449d1029baba41f8660</id>
<content type='text'>
When the upstream branch is tracked, we can detect if that branch
was rebased since it was last fetched.  Teach git to use that
information to rebase from the old remote head onto the new remote head.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>"git pull --tags": error out with a better message.</title>
<updated>2007-12-29T05:01:24Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2007-12-28T21:58:43Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=441ed4131b2d735fea08e4f6277c12b13acebd53'/>
<id>urn:sha1:441ed4131b2d735fea08e4f6277c12b13acebd53</id>
<content type='text'>
When "git pull --tags" is run without any other arguments, the
standard error message "You told me to fetch and merge stuff but
there is nothing to merge!  You might want to fix your config"
is given.

While the error may be technically correct, fixing the config
would not help, as "git pull --tags" itself tells "git fetch"
not to use the configured refspecs.

This commit makes "git pull --tags" to issue a different error
message to avoid confusion.  This is merely an interim solution.

In the longer term, it would be a better approach to change the
semantics of --tags option to make "git fetch" and "git pull"
to:

 (1) behave as if no --tags was given (so an explicit refspec on
     the command line overrides configured ones, or no explicit
     refspecs on the command line takes configured ones); but

 (2) no auto-following of tags is made even when using
     configured refspecs; and

 (3) fetch all tags as not-for-merge entries".

Then we would not need to have this separate error message, as
the ordinary merge will happen even with the --tags option.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Teach 'git pull' about --rebase</title>
<updated>2007-11-29T01:32:23Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>Johannes.Schindelin@gmx.de</email>
</author>
<published>2007-11-28T13:11:07Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=cd67e4d46b122b161f2ad7d943e4ae7aa8df6cf5'/>
<id>urn:sha1:cd67e4d46b122b161f2ad7d943e4ae7aa8df6cf5</id>
<content type='text'>
When calling 'git pull' with the '--rebase' option, it performs a
fetch + rebase instead of a fetch + merge.

This behavior is more desirable than fetch + pull when a topic branch
is ready to be submitted and needs to be update.

fetch + rebase might also be considered a better workflow with shared
repositories in any case, or for contributors to a centrally managed
repository, such as WINE's.

As a convenience, you can set the default behavior for a branch by
defining the config variable branch.&lt;name&gt;.rebase, which is
interpreted as a bool.  This setting can be overridden on the command
line by --rebase and --no-rebase.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>scripts: Add placeholders for OPTIONS_SPEC</title>
<updated>2007-11-06T09:50:02Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2007-11-06T09:50:02Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=8f321a39257a06db014a3b6ae5dce839821cdb16'/>
<id>urn:sha1:8f321a39257a06db014a3b6ae5dce839821cdb16</id>
<content type='text'>
--text follows this line--
These commands currently lack OPTIONS_SPEC; allow people to
easily list with "git grep 'OPTIONS_SPEC=$'" what they can help
improving.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Teach git-pull about --[no-]ff, --no-squash and --commit</title>
<updated>2007-10-29T20:32:52Z</updated>
<author>
<name>Lars Hjemli</name>
<email>hjemli@gmail.com</email>
</author>
<published>2007-10-29T08:41:18Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=5072a32382fb65fa7295811575d0f5c09cbe0dc3'/>
<id>urn:sha1:5072a32382fb65fa7295811575d0f5c09cbe0dc3</id>
<content type='text'>
These options are supported by git-merge, but git-pull didn't know about
them.

Signed-off-by: Lars Hjemli &lt;hjemli@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Make git-pull complain and give advice when there is nothing to merge with</title>
<updated>2007-10-03T00:27:48Z</updated>
<author>
<name>Federico Mena Quintero</name>
<email>federico@novell.com</email>
</author>
<published>2007-10-02T23:36:30Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=8fc293cb1e639c9ea555a8e95e3a7801fc1d1be8'/>
<id>urn:sha1:8fc293cb1e639c9ea555a8e95e3a7801fc1d1be8</id>
<content type='text'>
Signed-off-by: Federico Mena Quintero &lt;federico@gnu.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Supplant the "while case ... break ;; esac" idiom</title>
<updated>2007-09-23T23:12:00Z</updated>
<author>
<name>David Kastrup</name>
<email>dak@gnu.org</email>
</author>
<published>2007-09-23T20:42:08Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=822f7c7349d61f6075961ce42c1bd1a85cf999e5'/>
<id>urn:sha1:822f7c7349d61f6075961ce42c1bd1a85cf999e5</id>
<content type='text'>
A lot of shell scripts contained stuff starting with

	while case "$#" in 0) break ;; esac

and similar.  I consider breaking out of the condition instead of the
body od the loop ugly, and the implied "true" value of the
non-matching case is not really obvious to humans at first glance.  It
happens not to be obvious to some BSD shells, either, but that's
because they are not POSIX-compliant.  In most cases, this has been
replaced by a straight condition using "test".  "case" has the
advantage of being faster than "test" on vintage shells where "test"
is not a builtin.  Since none of them is likely to run the git
scripts, anyway, the added readability should be worth the change.

A few loops have had their termination condition expressed
differently.

Signed-off-by: David Kastrup &lt;dak@gnu.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Rewrite "git-frotz" to "git frotz"</title>
<updated>2007-07-03T05:52:14Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2007-07-03T05:52:14Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=5be60078c935ed08ee8eb5a32680bdfb6bb5bdf3'/>
<id>urn:sha1:5be60078c935ed08ee8eb5a32680bdfb6bb5bdf3</id>
<content type='text'>
This uses the remove-dashes target to replace "git-frotz" to "git frotz".

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Add a configuration option to control diffstat after merge</title>
<updated>2007-05-25T04:37:08Z</updated>
<author>
<name>Alex Riesen</name>
<email>raa.lkml@gmail.com</email>
</author>
<published>2007-05-23T21:01:29Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=51e7ecf4ecb506fb36cd5933cb7b78fb4b315ac9'/>
<id>urn:sha1:51e7ecf4ecb506fb36cd5933cb7b78fb4b315ac9</id>
<content type='text'>
The diffstat can be controlled either with command-line options
(--summary|--no-summary) or with merge.diffstat. The default is
left as it was: diffstat is active by default.

Signed-off-by: Alex Riesen &lt;raa.lkml@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-pull: disallow implicit merging to detached HEAD</title>
<updated>2007-01-15T23:37:22Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2007-01-15T22:25:33Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=a74b1706c89c5e966c64316575e0b33dd21b8128'/>
<id>urn:sha1:a74b1706c89c5e966c64316575e0b33dd21b8128</id>
<content type='text'>
Instead, we complain to the user and suggest that they explicitly
specify the remote and branch. We depend on the exit status of
git-symbolic-ref, so let's go ahead and document that.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
</feed>
