From: Nanako Shiraishi <nanako3@lavabit.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, ecashin@coraid.com, 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: What is not in git.git
Date: Thu, 05 Feb 2009 05:49:18 +0900 [thread overview]
Message-ID: <20090205054918.6117@nanako3.lavabit.com> (raw)
You keep mentioning 1.6.2 and I take it as a hint that the project is
approaching the pre release freeze. There are some patches sent to the
list that are not in git.git, and I am wondering what their statuses are.
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?
2. From: Arjen Laarhoven <arjen@yaph.org>
Subject: [PATCH 2/2] git-log: Follow file copies with 'git log --follow -C -C'
Date: Thu, 22 Jan 2009 17:37:25 +0100
Message-ID: <1232642245-94405-2-git-send-email-arjen@yaph.org>
Junio seemed to like the patch but asked a question; I did not see a
response nor updated patch (sorry, I do not read C and cannot comment
on the correctness of the patch).
3. From: Joey Hess <joey@kitenet.net>
Subject: [PATCH] gitweb: support the rel=vcs microformat
Date: Tue, 6 Jan 2009 23:25:18 -0500
Message-ID: <20090107042518.GB24735@gnu.kitenet.net>
A few exchanges of review comments and responses, and then this topic
went dark.
From: Benjamin Kramer <benny.kra@googlemail.com>
Subject: [PATCH] Makefile: Use libc strlcpy on OSX
Date: Sat, 24 Jan 2009 16:41:30 +0100
Message-ID: <7f978c810901240741k201f954dx1c0470186094ae24@mail.gmail.com>
My reading of the thread is that the only remaining issue was to limit
the change to specific versions, and I think people who use OSX can help
polish this topic to completion.
4. From: Pete Wyckoff <pw@padd.com>
Subject: [PATCH] git-p4: avoid syncing duplicate changes
Date: Wed, 28 Jan 2009 08:45:40 -0800
Message-ID: <20090128164540.GA2137@padd.com>
Nobody commented on this as far as I can tell. Do people not care
about p4? Simon Hausmann seem to be the most recent active contributor
and perhaps he can comment on this patch.
5. From: jidanni@jidanni.org
Subject: [PATCH] Documentation/git-show-branch.txt: compact -g
Date: Tue, 6 Jan 2009 11:14:02 +0800
Message-Id: <1231211642-14463-1-git-send-email-jidanni@jidanni.org>
I couldn't figure out what "compact -g" meant but other than that I
think this patch is correct. Perhaps Junio has the author in his mail
ignore list?
6. From: Alexander Potashev <aspotashev@gmail.com>
Subject: [PATCH] Replace deprecated dashed git commands in usage
Date: Sun, 4 Jan 2009 21:39:27 +0300
Message-ID: <1231094367-8831-1-git-send-email-aspotashev@gmail.com>
This should have been in 1.6.0 already but it is still not.
Forgotten?
7. From: Dirk Hörner <dirker@gmail.com>
Subject: [PATCH] git-cvsimport: add support for cvs pserver password scrambling.
Date: Fri, 28 Nov 2008 20:06:40 +0200
Message-ID: <5794AED2-43FF-4441-8292-0C9BFB3139A2@gmail.com>
I think Johannes Schindelin commented but then nothing happened to
this patch. Is there any more work necessary for its inclusion?
8. From: Heikki Hokkanen <hoxu@users.sf.net>
Subject: [PATCH] git show-ref: add --remotes option.
Date: Mon, 13 Oct 2008 22:23:47 +0300
Message-ID: <48F3A043.5070406@users.sf.net>
I saw no comments but it is consistent with how git-rev-list allows
you say branches and tags. Is there anything wrong with the patch?
--
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
next reply other threads:[~2009-02-04 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 20:49 Nanako Shiraishi [this message]
2009-02-04 22:49 ` What is not in git.git Junio C Hamano
2009-02-04 23:06 ` Joey Hess
2009-02-04 23:35 ` Nanako Shiraishi
2009-02-05 14:02 ` Ed Cashin
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=20090205054918.6117@nanako3.lavabit.com \
--to=nanako3@lavabit.com \
--cc=arjen@yaph.org \
--cc=benny.kra@googlemail.com \
--cc=dirker@gmail.com \
--cc=ecashin@coraid.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hoxu@users.sf.net \
--cc=jidanni@jidanni.org \
--cc=joey@kitenet.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox