From: Junio C Hamano <gitster@pobox.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Erick Mattos <erick.mattos@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH v2] git checkout -b: unparent the new branch with -o
Date: Sat, 13 Mar 2010 01:42:22 -0800 [thread overview]
Message-ID: <7vaaucd0ch.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <m38w9wlg7i.fsf@localhost.localdomain> (Jakub Narebski's message of "Sat\, 13 Mar 2010 01\:33\:19 -0800 \(PST\)")
Jakub Narebski <jnareb@gmail.com> writes:
> BUT in the case of 'html' and 'man' branches I could see why current
> implementation of _removing index and not removing files_ might be
> advantageous. Remove index, create HTML and manpage version of
> documentation, and add HTML (in 'html' branch) or manpages (in 'man'
> branch)... probably shifting root, so it is not all in single
> Documentation directory.
When you have some spare time, I'd recommend you to read dodoc.sh script
in the 'todo' branch. These preformatted documentation branches are
coming from their own repositories, very much on purpose.
> Just my 2 eurocents.
Already?
next prev parent reply other threads:[~2010-03-13 9:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 22:28 [PATCH v2] git checkout -b: unparent the new branch with -o Erick Mattos
2010-03-12 6:53 ` Junio C Hamano
2010-03-12 7:40 ` Bert Wesarg
2010-04-27 6:35 ` David Kågedal
2010-03-12 16:45 ` Erick Mattos
2010-03-13 7:53 ` Junio C Hamano
2010-03-13 9:10 ` Junio C Hamano
2010-03-14 21:57 ` Erick Mattos
2010-03-15 2:56 ` Junio C Hamano
2010-03-16 18:18 ` Erick Mattos
2010-03-13 9:33 ` Jakub Narebski
2010-03-13 9:42 ` Junio C Hamano [this message]
2010-03-14 21:57 ` Erick Mattos
2010-03-15 2:06 ` Junio C Hamano
2010-03-16 18:17 ` Erick Mattos
2010-03-14 20:46 ` Erick Mattos
2010-03-14 21:58 ` Erick Mattos
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=7vaaucd0ch.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=erick.mattos@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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).