* [TopGit PATCH] Clarify tg-log note
@ 2010-10-22 8:03 Bert Wesarg
2010-10-22 8:43 ` Uwe Kleine-König
0 siblings, 1 reply; 3+ messages in thread
From: Bert Wesarg @ 2010-10-22 8:03 UTC (permalink / raw)
To: Uwe Kleine-Koenig
Cc: Per Cederqvist, git, pasky, martin f krafft, Bert Wesarg
---
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.
TODO: tg rename
--
1.7.3.1.1075.g263d8
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [TopGit PATCH] Clarify tg-log note
2010-10-22 8:03 [TopGit PATCH] Clarify tg-log note Bert Wesarg
@ 2010-10-22 8:43 ` Uwe Kleine-König
2010-10-22 8:57 ` Bert Wesarg
0 siblings, 1 reply; 3+ messages in thread
From: Uwe Kleine-König @ 2010-10-22 8:43 UTC (permalink / raw)
To: Bert Wesarg; +Cc: Per Cederqvist, git, pasky, martin f krafft
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/ |
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [TopGit PATCH] Clarify tg-log note
2010-10-22 8:43 ` Uwe Kleine-König
@ 2010-10-22 8:57 ` Bert Wesarg
0 siblings, 0 replies; 3+ messages in thread
From: Bert Wesarg @ 2010-10-22 8:57 UTC (permalink / raw)
To: Uwe Kleine-König; +Cc: Per Cederqvist, git, pasky, martin f krafft
2010/10/22 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> 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.
Yeah, sounds perfect ;-)
Bert
>
> Best regards
> Uwe
>
> --
> Pengutronix e.K. | Uwe Kleine-König |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-10-22 8:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-22 8:03 [TopGit PATCH] Clarify tg-log note Bert Wesarg
2010-10-22 8:43 ` Uwe Kleine-König
2010-10-22 8:57 ` Bert Wesarg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox