git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Drew Northup <n1xim.email@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Max Horn <max@quendi.de>,
	John Keeping <john@keeping.me.uk>,
	git@vger.kernel.org, Scott Chacon <schacon@gmail.com>
Subject: Re: Anybody know a website with up-to-date git documentation?
Date: Sun, 17 Feb 2013 08:21:25 -0500	[thread overview]
Message-ID: <CAM9Z-nmoCQ-uXwMCxCn4iRjUrxDf1r9Rb1ap_PQSra-FneECAA@mail.gmail.com> (raw)
In-Reply-To: <20130130230709.GA7787@sita-lt.atc.tcs.com>

On Wed, Jan 30, 2013 at 6:07 PM, Sitaram Chamarty <sitaramc@gmail.com> wrote:
> On Wed, Jan 30, 2013 at 09:18:24AM -0800, Junio C Hamano wrote:
>> Max Horn <max@quendi.de> writes:
>> > On 30.01.2013, at 16:59, Sitaram Chamarty wrote:
>> >
>> >> I'm curious... what's wrong with 'git checkout html' from the git repo
>> >> and just browsing them using a web browser?

>> Armed with that knowledge, I think Sitaram may have something like
>> this:
>>
>>       [remote "htmldocs"]

> Hmm; I don't recall ever doing that.  But I just realised that
> my "html" branch is stuck at 1.7.7:
>
>     $ git branch -v -v | grep html
>       html   8fb66e5 [origin/html] Autogenerated HTML docs for v1.7.7-138-g7f41b6
>
> Is it possible that upto that point, the main git.git repo did
> carry this branch also?

Yes.

n1xim@atom:~/tmp/git_dev/git$ git branch -a
  dn/utf16_check
* master
  remotes/origin/HEAD -> origin/master
  remotes/origin/html
  remotes/origin/maint
  remotes/origin/man
  remotes/origin/master
  remotes/origin/next
  remotes/origin/pu
  remotes/origin/todo
n1xim@atom:~/tmp/git_dev/git$ git remote show origin
* remote origin
  Fetch URL: git://git.kernel.org/pub/scm/git/git.git
  Push  URL: git://git.kernel.org/pub/scm/git/git.git
  HEAD branch: master
  Remote branches:
    maint                    tracked
    master                   tracked
    next                     tracked
    pu                       tracked
    refs/remotes/origin/html stale (use 'git remote prune' to remove)
    refs/remotes/origin/man  stale (use 'git remote prune' to remove)
    todo                     tracked
  Local branch configured for 'git pull':
    master merges with remote master
  Local ref configured for 'git push':
    master pushes to master (local out of date)

n1xim@atom:~/tmp/git_dev/git$ git log refs/remotes/origin/html
commit 5723afaf3a61cef537e1f4dfa88f8faf31060ef0
Author: Junio C Hamano <junio@kernel.org>
Date:   Wed Aug 31 00:49:23 2011 +0000

    Autogenerated HTML docs for v1.7.7-rc0-72-g4b5ea

n1xim@atom:~/tmp/git_dev/git$ git log refs/remotes/origin/man
commit e193e4189407968b3c46992e3eac60d38424286e
Author: Junio C Hamano <junio@kernel.org>
Date:   Wed Aug 31 00:49:25 2011 +0000

    Autogenerated manpages for v1.7.7-rc0-72-g4b5ea

....I haven't bothered to plunge and expunge my local repo yet as I
never actually made use of those branches.

-- 
-Drew Northup
--------------------------------------------------------------
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59

  reply	other threads:[~2013-02-17 13:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 11:46 Anybody know a website with up-to-date git documentation? Max Horn
2013-01-30 11:54 ` John Keeping
2013-01-30 11:56   ` Sebastian Staudt
2013-01-30 13:27     ` Max Horn
2013-01-30 13:48       ` Sebastian Staudt
2013-01-30 13:58   ` Max Horn
2013-01-30 15:59     ` Sitaram Chamarty
2013-01-30 17:05       ` Max Horn
2013-01-30 17:18         ` Junio C Hamano
2013-01-30 23:07           ` Sitaram Chamarty
2013-02-17 13:21             ` Drew Northup [this message]
2013-01-30 16:46 ` Junio C Hamano

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM9Z-nmoCQ-uXwMCxCn4iRjUrxDf1r9Rb1ap_PQSra-FneECAA@mail.gmail.com \
    --to=n1xim.email@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=john@keeping.me.uk \
    --cc=max@quendi.de \
    --cc=schacon@gmail.com \
    --cc=sitaramc@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.
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 NNTP newsgroup(s).