On 18/05/2019 13:17, Duy Nguyen wrote:
On Tue, May 14, 2019 at 6:10 PM Philip Oakley wrote:
It is a 'branch which tracks a remote', and it is has the 'last time I
looked' state of the branch that is on the remote server, which may
have, by now, advanced or changed.
So you need to have the thre
On Tue, May 14, 2019 at 6:10 PM Philip Oakley wrote:
> >> It is a 'branch which tracks a remote', and it is has the 'last time I
> >> looked' state of the branch that is on the remote server, which may
> >> have, by now, advanced or changed.
> >>
> >> So you need to have the three distinct views i
On 15/05/2019 09:45, Ulrich Windl wrote:
reasoning for that.
It's that you are missing the idea behind the "Branches that track the
remote", which are local copies, but not YOUR branches. see below.
I clone the GitHub test repo. I get (a copy of) it all (the rtb's). Git
_creates_ a local branch '
>>> Philip Oakley schrieb am 15.05.2019 um 09:34 in
Nachricht :
> On 14/05/2019 12:49, Ulrich Windl wrote:
>> Hi!
>>
>> The confusing part actually is for me:
>> "git clone" does NOT "Clone a repository into a new directory", but "clone
> the current branch into a new directory" (IMHO).
>> So I w
On 14/05/2019 12:49, Ulrich Windl wrote:
Hi!
The confusing part actually is for me:
"git clone" does NOT "Clone a repository into a new directory", but "clone the
current branch into a new directory" (IMHO).
So I was surprised that I couldn't merge branches under the same name in the cloned
"r
On 15/05/2019 02:50, Junio C Hamano wrote:
Philip Oakley writes:
It is a 'branch which tracks a remote', and it is has the 'last time I
looked' state of the branch that is on the remote server, which may
have, by now, advanced or changed.
Yup, I thought we long time ago decided to discourage
Philip Oakley writes:
> It is a 'branch which tracks a remote', and it is has the 'last time I
> looked' state of the branch that is on the remote server, which may
> have, by now, advanced or changed.
Yup, I thought we long time ago decided to discourage use of "remote
branch(es)" in our docume
Hi!
The confusing part actually is for me:
"git clone" does NOT "Clone a repository into a new directory", but "clone the
current branch into a new directory" (IMHO).
So I was surprised that I couldn't merge branches under the same name in the
cloned "repository".
Only "git clone --bare" actuall
Hi Duy,
On 14/05/2019 11:53, Duy Nguyen wrote:
On Tue, May 14, 2019 at 5:33 PM Philip Oakley wrote:
Hi Ulrich,
On 14/05/2019 11:12, Duy Nguyen wrote:
Then I
foundhttps://stackoverflow.com/questions/10312521/how-to-fetch-all-git-branches
which handles the subject...
But still the most commo
On Tue, May 14, 2019 at 5:33 PM Philip Oakley wrote:
>
> Hi Ulrich,
> On 14/05/2019 11:12, Duy Nguyen wrote:
> >> Then I
> >> foundhttps://stackoverflow.com/questions/10312521/how-to-fetch-all-git-branches
> >> which handles the subject...
> >> But still the most common solution there still loo
Hi Ulrich,
On 14/05/2019 11:12, Duy Nguyen wrote:
Then I
foundhttps://stackoverflow.com/questions/10312521/how-to-fetch-all-git-branches
which handles the subject...
But still the most common solution there still looks like an ugly hack.
Thus I suggest to improve the man-pages (unless done alr
On Tue, May 14, 2019 at 4:42 PM Ulrich Windl
wrote:
>
> Hi!
>
> While wondering why some branches are not being displayed by "git branch" in
> a cloned repository, I was reading the obvious man pages (man git-branch, man
> git-remote), but still couldn't find the reason or the solution.
Local a
Hi!
While wondering why some branches are not being displayed by "git branch" in a
cloned repository, I was reading the obvious man pages (man git-branch, man
git-remote), but still couldn't find the reason or the solution. Then I found
https://stackoverflow.com/questions/10312521/how-to-fetch-
13 matches
Mail list logo
