From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [GSoC] Some #leftoverbits for anyone looking for little projects
Date: Wed, 29 May 2019 11:40:24 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1905291139460.44@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1905291137070.44@tvgsbejvaqbjf.bet>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
Hi,
On Wed, 29 May 2019, Johannes Schindelin wrote:
> On Sat, 17 Mar 2018, Ævar Arnfjörð Bjarmason wrote:
>
> > In lieu of sending a PR to https://git.github.io/SoC-2018-Microprojects/
> > I thought I'd list a few more suggestions, and hopefully others will
> > chime in.
>
> I am in the same camp, and figured that GitGitGadget (which *already*
> augments the Git mailing list-centric workflow via GitHub's convenient UI)
> would make for a fine location for these small left-over bits. So I added
> them to https://github.com/gitgitgadget/git/issues/234 (except the
Of course, I added them to https://github.com/gitgitgadget/git/issues/,
with #234 being the last from this email.
Ciao,
Dscho
> "git-unpack-*" idea, as I think that should be done as a test helper
> instead, and it should be done in the context of a new test case that
> actually needs this).
>
> Ciao,
> Dscho
next prev parent reply other threads:[~2019-05-29 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 21:20 [GSoC] Some #leftoverbits for anyone looking for little projects Ævar Arnfjörð Bjarmason
2019-05-20 18:23 ` Matheus Tavares
2019-05-20 23:49 ` Ævar Arnfjörð Bjarmason
2019-05-21 4:38 ` Matheus Tavares Bernardino
2019-05-28 10:37 ` Johannes Schindelin
2019-05-28 17:37 ` Matheus Tavares Bernardino
2019-05-28 18:16 ` Johannes Schindelin
2019-05-29 9:38 ` Johannes Schindelin
2019-05-29 9:40 ` Johannes Schindelin [this message]
[not found] ` <20220318220623.50528-1-gaurijove@gmail.com>
[not found] ` <CANsrJQdNKiX93GnVXztmvYQQBxr6-HsYNx5UvYXSFg32Op3ZPQ@mail.gmail.com>
[not found] ` <CANsrJQe1YuggxdBHdSdukXRj3myVCTNwLiiWNLrAzPpzA4FOOA@mail.gmail.com>
[not found] ` <220319.86ee2yds2f.gmgdl@evledraar.gmail.com>
[not found] ` <CANsrJQdJ1wBThUyJ=QSt6NwU8HzQY2VaWc11UfZQ+ktRQs_YTQ@mail.gmail.com>
[not found] ` <220319.86a6dlewyj.gmgdl@evledraar.gmail.com>
2022-03-20 19:14 ` Having grep support the -o option Jayati Shrivastava
2022-03-22 6:08 ` Christian Couder
2022-03-22 10:50 ` Ævar Arnfjörð Bjarmason
2022-03-23 17:45 ` Jayati Shrivastava
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1905291139460.44@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=avarab@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).