From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: <git@vger.kernel.org>
Subject: Antw: Re: Missing branches after clone
Date: Tue, 14 May 2019 13:49:42 +0200 [thread overview]
Message-ID: <5CDAAB56020000A100031334@gwsmtp.uni-regensburg.de> (raw)
In-Reply-To: <0c9ec78a-9245-e1df-7ec6-a5d77d1a5261@iee.org>
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" actually seems to clone "the repository".
I think this is very confusing to new users. At least I didn't quite get the reasoning for that.
Regards,
Ulrich
>>> Philip Oakley <philipoakley@iee.org> schrieb am 14.05.2019 um 12:33 in
Nachricht <0c9ec78a-9245-e1df-7ec6-a5d77d1a5261@iee.org>:
> Hi Ulrich,
> On 14/05/2019 11:12, Duy Nguyen wrote:
>>> Then I
> foundhttps://stackoverflow.com/questions/10312521/how-to-fetch-all-git-branch
> es 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 already)
>> Yeah I expected to see at least some definition of remote-tracking
>> branches (vs local ones) but I didn't see one. Room for improvement.
> Yes, the 'remote tracking branch' name [RTB] is very 'French' in its
> backwardness (see NATO/OTAN).
>
> 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 in your head of 'My branch,
> held locally', 'my copy of Their branch, from when I last looked', and
> 'Their branch, on a remote server, in a state I haven't seen recently'.
>
> Finding a better name for the "RTB", one with an easier cognitive load
> for those trying to understand Git, would be an improvement.
>
> Though there has been a similar issue with 'staging the index'.
> Ultimately it is a new way of thinking about artefacts (perfect
> duplicates, no originals, no master, no copies, just verification
> hashes) so needs new terms and a difficult learning experience.
> --
> Philip
next prev parent reply other threads:[~2019-05-14 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 9:41 Missing branches after clone Ulrich Windl
2019-05-14 10:12 ` Duy Nguyen
2019-05-14 10:33 ` Philip Oakley
2019-05-14 10:53 ` Duy Nguyen
2019-05-14 11:10 ` Philip Oakley
2019-05-18 12:17 ` Duy Nguyen
2019-05-19 0:09 ` Philip Oakley
2019-05-14 11:49 ` Ulrich Windl [this message]
2019-05-15 7:34 ` Antw: " Philip Oakley
2019-05-15 8:45 ` Ulrich Windl
2019-05-15 13:07 ` Philip Oakley
2019-05-15 1:50 ` Junio C Hamano
2019-05-15 7:13 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5CDAAB56020000A100031334@gwsmtp.uni-regensburg.de \
--to=ulrich.windl@rz.uni-regensburg.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).