From: Ed Cashin <ecashin@coraid.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nanako Shiraishi <nanako3@lavabit.com>,
git@vger.kernel.org, arjen@yaph.org, joey@kitenet.net,
benny.kra@googlemail.com, pw@padd.com, simon@lst.de,
jidanni@jidanni.org, dirker@gmail.com, hoxu@users.sf.net
Subject: Re: What is not in git.git
Date: Thu, 5 Feb 2009 09:02:15 -0500 [thread overview]
Message-ID: <20090205140215.GB20348@coraid.com> (raw)
In-Reply-To: <7vy6wllswz.fsf@gitster.siamese.dyndns.org>
On Wed, Feb 04, 2009 at 02:49:00PM -0800, Junio C Hamano wrote:
> Nanako Shiraishi <nanako3@lavabit.com> writes:
...
> > 1. From: ecashin@coraid.com
> > Subject: [PATCH] git-describe documentation: --match pattern is glob
> > Date: Thu, 22 Jan 2009 11:21:53 -0500
> > Message-ID: <dfa634dbd8def9e205bbe219217179ca@coraid.com>
> >
> > I thought this was correct, but was missing a sign-off. Perhaps it was
> > dropped on the floor because it was sent in a wrong format that is
> > harder to apply?
>
> Mostly correct, but because we consider refnames like filesystem paths and
> the use of globs when matching them is shared as the same basic design
> across commands, I do not think the manual page for each individual
> command is the right place to say it.
I can add a sign-off if that would help, but it sounds like it was the
wrong fix. I didn't know the right place to say it, but I figure: If
there is a right place, then what is it? If there isn't one, saying
it in the git-describe manpage is probably a good step for now.
--
Ed Cashin <ecashin@coraid.com>
prev parent reply other threads:[~2009-02-05 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 20:49 What is not in git.git Nanako Shiraishi
2009-02-04 22:49 ` Junio C Hamano
2009-02-04 23:06 ` Joey Hess
2009-02-04 23:35 ` Nanako Shiraishi
2009-02-05 14:02 ` Ed Cashin [this message]
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=20090205140215.GB20348@coraid.com \
--to=ecashin@coraid.com \
--cc=arjen@yaph.org \
--cc=benny.kra@googlemail.com \
--cc=dirker@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hoxu@users.sf.net \
--cc=jidanni@jidanni.org \
--cc=joey@kitenet.net \
--cc=nanako3@lavabit.com \
--cc=pw@padd.com \
--cc=simon@lst.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.