Re: [PATCH] sha1_name.c: update comment to mention :/foo syntax
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 21, 2010, 18:02 UTC
- Message-ID
- <7v62xzug94.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <1285016477-22222-1-git-send-email-Matthieu.Moy@imag.fr>
Matthieu Moy <Matthieu.Moy@imag.fr> writes:
Show 17 quoted lines
> Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr> > --- > Noticed while reviewing the patch serie about textconv and symlinks. > If we have comments, better have them up-to-date ;-). > > sha1_name.c | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/sha1_name.c b/sha1_name.c > index 7b7e617..d7ab72a 100644 > --- a/sha1_name.c > +++ b/sha1_name.c > @@ -1062,6 +1062,7 @@ int get_sha1_with_context_1(const char *name, unsigned char *sha1, > /* sha1:path --> object name of path in ent sha1 > * :path -> object name of path in index > * :[0-3]:path -> object name of path in index at stage > + * :/foo -> last commit whose subject starts with foo
Documenting what hasn't been is a good thing, but is it really up-to-date?
Isn't it "a randomly chosen recent commit whose subject contains regexp foo" these days?