On Mon, Oct 8, 2012 at 7:33 PM, Junio C Hamano gits...@pobox.com wrote:
Junio C Hamano gits...@pobox.com writes:
In other words, you can do this from the command line if you want
to do the update.
$ git fetch origin master:refs/remotes/origin/master
Now having said all that, we should
Drew Northup n1xim.em...@gmail.com writes:
On Mon, Oct 8, 2012 at 7:33 PM, Junio C Hamano gits...@pobox.com wrote:
Junio C Hamano gits...@pobox.com writes:
I personally do not think the downside of breaking backward
compatibility is too bad. If we do this only when we already are
Angelo Borsotti angelo.borso...@gmail.com writes:
git fetch repository refspec does not create the remote refs in
the current (local)
repository...
However, if a git fetch origin is executed, the refs are properly created:
Working as designed and documented.
$ git fetch origin master
is
Junio C Hamano gits...@pobox.com writes:
Angelo Borsotti angelo.borso...@gmail.com writes:
git fetch repository refspec does not create the remote refs in
the current (local)
repository...
However, if a git fetch origin is executed, the refs are properly created:
Working as designed and
Junio C Hamano gits...@pobox.com writes:
In other words, you can do this from the command line if you want
to do the update.
$ git fetch origin master:refs/remotes/origin/master
Now having said all that, we should probably revisit this and
possibly other issues and for the ones we can
On Tue, Oct 9, 2012 at 6:33 AM, Junio C Hamano gits...@pobox.com wrote:
* Unify pathspec semantics
This has happened and commands that used to take only path prefix
style pathspecs now take globs as well [ND]
I've been thinking about it lately and will probably restart soon with
a
6 matches
Mail list logo