git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.org>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Missing branches after clone
Date: Sun, 19 May 2019 01:09:35 +0100	[thread overview]
Message-ID: <033ba463-dddd-d5b8-903c-9729190c213a@iee.org> (raw)
In-Reply-To: <CACsJy8Cc+cj0kC5=N+6AGB2UGDWA3uK946vgdhg9Cpx9a7w2wg@mail.gmail.com>

On 18/05/2019 13:17, Duy Nguyen wrote:
> On Tue, May 14, 2019 at 6:10 PM Philip Oakley <philipoakley@iee.org> 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 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'.
>>> What I was looking for is this. I don't think we have something like
>>> this in the man pages (I only checked a few though) and not even sure
>>> where it should be if it should be added to the man pages, git-branch?
>>> git-remote? git-fetch? git-branch.txt might be the best place because
>>> this is still about branches.
>>>
>> At the moment its in `git help glossary`, but could be improved, and
>> references to it given in the various man pages.
> It does not look easy to link to a specific term/section between man
> pages. The way user-manual.html does it is to embed the whole
> glossary.
>
> I suppose we could still do something similar after breaking down
> glossary.txt (like we do with config.txt) the only include relevant
> terms. Not sure if this a really good idea to pursue.
Mainly I was commenting on the fact that the description is in a guide 
(which isn't well known).
And that we rarely give links to the guides.
For those that end up using the HTML man pages, having hyperlinks to the 
particular section would be useful, though I'm not sure if their is a 
neat way of doing that which is 'nice' for those using the 'man' viewer.
So yes, it's more of a back burner issue, unless some eager tech authors 
suddenly show up;-)
--
Philip

  reply	other threads:[~2019-05-19  0:09 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 [this message]
2019-05-14 11:49     ` Antw: " Ulrich Windl
2019-05-15  7:34       ` 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=033ba463-dddd-d5b8-903c-9729190c213a@iee.org \
    --to=philipoakley@iee.org \
    --cc=Ulrich.Windl@rz.uni-regensburg.de \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    /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).