From: fork0@t-online.de (Alex Riesen)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: RFH: refactor read-tree
Date: Sun, 9 Jul 2006 14:43:24 +0200 [thread overview]
Message-ID: <20060709124324.GE5919@steel.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0607082011060.5623@g5.osdl.org>
Linus Torvalds, Sun, Jul 09, 2006 05:15:41 +0200:
> The basic idea is that "branch1" should be your current branch, and it
> obviously is also expected to match (more or less) the current index. So
> you can do a merge by
>
> - reading in "branch1" into the index:
>
> GIT_INDEX_FILE=.git/tmp-index git-read-tree -m branch1
what is "-m" here for?
next prev parent reply other threads:[~2006-07-09 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 22:28 RFH: refactor read-tree Johannes Schindelin
2006-07-09 3:15 ` Linus Torvalds
2006-07-09 12:43 ` Alex Riesen [this message]
2006-07-09 14:30 ` Johannes Schindelin
2006-07-09 15:30 ` Linus Torvalds
2006-07-09 22:17 ` Alex Riesen
2006-07-09 14:55 ` Johannes Schindelin
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=20060709124324.GE5919@steel.home \
--to=fork0@t-online.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=torvalds@osdl.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox