From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: git@vger.kernel.org
Subject: Re: Confusing language in man page
Date: Sun, 15 Jul 2007 01:57:52 +0530 [thread overview]
Message-ID: <a781481a0707141327k5b6f8f43sc6330ff8cc504dd1@mail.gmail.com> (raw)
In-Reply-To: <a781481a0707141108g4664a627w94e0d21c3629cb49@mail.gmail.com>
On 7/14/07, Satyam Sharma <satyam.sharma@gmail.com> wrote:
> Hi,
>
> [ I'm using Fedora's latest package. ]
I should probably clarify:
$ git --version
git version 1.5.0.6
Perhaps man pages / functionality have been updated significantly
since that, so let me know if that's the case.
> From git-checkout(1) and git-branch(1):
>
> -l Create the new branch's ref log. This activates recording of
> all changes to made the
> branch ref, enabling use of date
>
> I'd be glad if someone could explain that a bit more verbosely
> in the man page
> (or just here in a reply), or at least make that grammatically
> correct/readable :-)
Ok, another confusion I hit (as I learn more about git) tonight:
* What exactly is the use of git-diff's "-p" option?
$ git diff
and
$ git diff -p
produce the same output / do the same thing -- the man page mentions
"Generate patch (see section on generating patches)" but I couldn't find
said section (is that referring to some other man page?)
* On my system, doing:
$ git diff
with no outstanding changes in my current working tree produces some
bogus newlines, throwing the prompt to the bottom of the xterm window.
This sounds like weird / undesirable behaviour and I have a feeling must
already be fixed in latest git (?)
Thanks,
Satyam
next prev parent reply other threads:[~2007-07-14 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 18:08 Confusing language in man page Satyam Sharma
2007-07-14 20:27 ` Satyam Sharma [this message]
2007-07-15 9:40 ` Alex Riesen
2007-07-15 21:25 ` Satyam Sharma
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=a781481a0707141327k5b6f8f43sc6330ff8cc504dd1@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).