git mailing list

FromSubjectsort iconDate
Junio C Hamano
Re: git pull and merging.
In other words, I am all for fixing this. Although it may not hurt too much if we just redefine the meaning of it to name the local tracking branch, using a different name "branch.*.defaultmerge" is safer and would not break existing repositories. -
Dec 7, 7:06 pm 2006
sbejar
Re: git pull and merging.
Or branch.*.localmerge? Santi -
Dec 7, 10:04 pm 2006
Josef Weidendorfer
Re: git pull and merging.
Hmm... that's true; actually, I did not thought about people which do not want to have any tracking branches (again!). So [remote "repo"] url = ... fetch = branch1 fetch = branch2 [branch "mybranch1"] remote = repo merge = branch1 actually looks fine, and is the only possible way. But still, this does not work. You have to specify merge = refs/heads/branch1 That's confusing (perhaps I can come up with a patch to allow "branch1" alone). So probably the best way is to w...
Dec 7, 6:54 pm 2006
sbejar
Re: git pull and merging.
It does not. Perhaps that the branch.<name>.remote and branch.<name>.merge have the -
Dec 7, 9:56 pm 2006
Eric Wong
Re: [PATCH 5/5] git-svn: re-map repository URLs and UUIDs on...
For the git-svn in master using the delta fetcher; there's no additional overhead to fetch properties. I want to ditch the old non-delta fetching code (it's only a mild performance benefit when using local repositories) if I could get do_switch() working correctly. -- Eric Wong -
Dec 7, 4:02 pm 2006
previous daytodaynext day
December 6, 2006December 7, 2006December 8, 2006