From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: Per Cederqvist <ceder@lysator.liu.se>,
git@vger.kernel.org, pasky@suse.cz,
martin f krafft <madduck@madduck.net>
Subject: Re: [TopGit PATCH] Clarify tg-log note
Date: Fri, 22 Oct 2010 10:43:58 +0200 [thread overview]
Message-ID: <20101022084358.GE19834@pengutronix.de> (raw)
In-Reply-To: <0ecc03501a8282e7c19011ca1cbc138dec502390.1287734568.git.bert.wesarg@googlemail.com>
On Fri, Oct 22, 2010 at 10:03:36AM +0200, Bert Wesarg wrote:
> ---
> README | 13 +++++++++----
> 1 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/README b/README
> index 5ca0424..348f515 100644
> --- a/README
> +++ b/README
> @@ -520,10 +520,15 @@ tg log
> ~~~~~~
> Prints the git log of the named topgit branch.
>
> - Note: if you have shared the TopGit branch, this command
> - only lists the commits that were made in the current
> - repository, so you will not see work done by your
> - collaborators.
> + Note: that you don't see changes made by the remote
> + when the topic diverged at both sides. Any 'fast-forward'
> + updates from remote topics will shown up. This could also
> + mean, that you 'lose' all your history, because the remote
> + made the merge and you do only a 'fast-forward'. Than you
> + will see only his history from now on. So its best to prevent
> + diverging development if you like to 'preserve' the full
> + history. Please note, that 'lose' and 'preserve' only relates
> + to when showing the log.
Hmm, I see your intention, but I wonder if it wouldn't be enough to say:
Note: if you have merged changes from a different repository, this
command might not list all interesting commits.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-10-22 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 8:03 [TopGit PATCH] Clarify tg-log note Bert Wesarg
2010-10-22 8:43 ` Uwe Kleine-König [this message]
2010-10-22 8:57 ` Bert Wesarg
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=20101022084358.GE19834@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=bert.wesarg@googlemail.com \
--cc=ceder@lysator.liu.se \
--cc=git@vger.kernel.org \
--cc=madduck@madduck.net \
--cc=pasky@suse.cz \
/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