git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: Re: merging initial part of a branch?
Date: Fri, 13 Jan 2006 11:50:44 -0800	[thread overview]
Message-ID: <7v4q477vqj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20060113151005.GA29804@fieldses.org

"J. Bruce Fields" <bfields@fieldses.org> writes:

> ....  Plain git
> actually seems to have pretty usable interfaces at this point, but it's
> not always obvious where to find them....

I share that feeling too, especially in the documentation area.

Last time we had something very nice going on in this thread:

    http://thread.gmane.org/gmane.comp.version-control.git/12917

whose the key article is:

    http://article.gmane.org/gmane.comp.version-control.git/13360

but the general sentiment was that having another document is
making things more confusing and we should try to clarify the
main documentation instead. Pasky said aptly:

    http://article.gmane.org/gmane.comp.version-control.git/13410

I am not much of a documentation person myself, and I do not
have much interaction with people new to git, without which it
is hard to know which point is harder to grasp and what
documentation pages assume certain things are known to an
uninitiated when they should not.

So I would really appreciate documentaiotn patches to clarify
the current mess ;-).

> I also have Yet Another Git Tutorial, at
> http://www.fieldses.org/~bfields/kernel/git.html.  (Corrections and
> suggestions welcomed.)

The $prefix defaults to $HOME/bin/.  Having $bindir on $PATH
ought to be enough and exporting GIT_EXEC_PATH is not needd.

Other than that I did not see anything obviously wrong, although
I suspect you did not intend to say clone with stgit.

  reply	other threads:[~2006-01-13 19:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 23:04 merging initial part of a branch? J. Bruce Fields
2006-01-11 23:47 ` Junio C Hamano
2006-01-12  0:15   ` Andreas Ericsson
2006-01-12  0:24     ` Junio C Hamano
2006-01-12  0:59       ` Andreas Ericsson
2006-01-12  1:13         ` J. Bruce Fields
2006-01-12  0:55   ` J. Bruce Fields
2006-01-12  1:47     ` Junio C Hamano
2006-01-13  3:08       ` J. Bruce Fields
2006-01-13  4:00         ` Junio C Hamano
2006-01-13 15:10           ` J. Bruce Fields
2006-01-13 19:50             ` Junio C Hamano [this message]
2006-01-13 20:01               ` J. Bruce Fields
     [not found]                 ` <20060115185458.GA3985@fieldses.org>
2006-01-15 23:26                   ` [PATCH] new tutorial Junio C Hamano
2006-01-16  3:57                     ` J. Bruce Fields
2006-01-16  5:32                       ` Junio C Hamano
2006-01-23  4:57                     ` J. Bruce Fields

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=7v4q477vqj.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=bfields@fieldses.org \
    --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).