From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: Git Mailing List <git@vger.kernel.org>
Subject: Documentation Bugs
Date: Sun, 6 May 2007 15:09:22 +0200 [thread overview]
Message-ID: <20070506130921.GA3750@lala> (raw)
Hello,
1) git-fetch(1) (from maint) states:
-q, --quiet
Pass --quiet to git-fetch-pack and silence any other internally
used programs.
but git-fetch doesn't like -q. (master has
a858c006fae17cef44dd63737771f2bebb6eeae8, but maint only has
42905294de0c1885f5636319c4790f184d767875)
Maybe more difficult:
2) rebase a merged tree:
If I made a local commit and pulled from origin, I get:
zeisberg@cassiopeia:~/gsrc/git$ git show
commit 15386213004a20dfdf92c654c737795079202545
Merge: 9d740f0... 9159afb...
Author: Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
Date: Sun May 6 14:49:59 2007 +0200
Merge branch 'master' of git://git.kernel.org/pub/scm/git/git
zeisberg@cassiopeia:~/gsrc/git$ git rebase junio/master
Current branch master is up to date.
(where junio/master is the tracking branch for
git://git.kernel.org/pub/scm/git/git) but git-rebase(1) states:
All changes made by commits in the current branch but that are
not in <upstream> are saved to a temporary area. This is the
same set of commits that would be shown by git log
<upstream>..HEAD.
and git-log junio/master..HEAD is not empty.
I didn't have the time to look into 2). So I only report it for now.
Best regards
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=sin%28pi%2F2%29
next reply other threads:[~2007-05-06 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 13:09 Uwe Kleine-König [this message]
2007-05-07 12:58 ` Documentation Bugs Uwe Kleine-König
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=20070506130921.GA3750@lala \
--to=ukleinek@informatik.uni-freiburg.de \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox