On Mon, Oct 4, 2010 at 06:40, Per Cederqvist [off-list ref] wrote:
Using --first-parent to get only the interesting commits only works reliably
when you only work locally. If you collaborate and you and your partner both
make a commit before you push to a central server you will have to make a
merge, where both parents are interesting.
I wish that git remembered which branch a commit was initially made on. That
would make "tg log" easy to implement correctly. But since git doesn't, I
don't think it is possible to implement it properly.
At least, a warning should be added to the README.
I've read it from your tg base help message and have no problem to
copy/move it to tg log.
Bert
/ceder
Signed-off-by: Bert Wesarg <redacted>
---
README | 15 ++++++---------
1 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/README b/README
index ce0c3a6..2331117 100644 README
--- a/README
+++ b/README
@@ -514,20 +514,17 @@ tg base
~~~~~~~
Prints the base commit of the current topic branch. Silently
exits with exit code 1 if you are not working on a TopGit
- branch. The following command can be useful to get a summary
- of the work you have made on a topic branch:
-
- git log --first-parent --no-merges `tg base`..
-
- (Note: if you have shared the TopGit branch, the above command
- only lists the commits that were made in the current
- repository, so you will not see work done by your
- collaborators.)
+ branch.
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 where made in the current
+ repository, so you will not see work done by your
+ collaborators.
+
TODO: tg rename
--
tg: (ff59ac7..) bw/log (depends on: master)