From: Christian Couder <christian.couder@gmail.com>
To: Antoine Delaite <antoine.delaite@ensimag.grenoble-inp.fr>
Cc: git <git@vger.kernel.org>,
Alexandre Stuber <stuberl@ensimag.grenoble-inp.fr>,
galanalr@ensimag.grenoble-inp.fr,
lespiner@ensimag.grenoble-inp.fr, pagesg@ensimag.grenoble-inp.fr,
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Subject: Re: Ensimag students contributing to git
Date: Tue, 19 May 2015 17:47:15 +0200 [thread overview]
Message-ID: <CAP8UFD16vb_-rp7kiATd=XW5FK+P+qkME8hPMku571_PDCQywg@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD2hCScvEZxxFCc4XWLJuHM-SyqZ_x4sdmwXj8WVHrW4tQ@mail.gmail.com>
On Tue, May 19, 2015 at 5:10 PM, Christian Couder
<christian.couder@gmail.com> wrote:
>
> Last Autumn I started to work a bit on « git bisect fix/unfixed » (or
> more accurately « git bisect old/new ») by applying and reworking a
> bit what your Ensimag elders had done. It is not much but maybe it can
> help you a bit.
>
> It is on this branch on my github repo:
>
> https://github.com/chriscool/git/commits/boldnew1
>
> There are only 3 original patches on this branch. The first one is
> what your elders did and the other 2 are some small cleanups on top.
>
> You will need to rebase and rework this, but it is a start.
Actually I rebased it on current master and it is available here:
https://github.com/chriscool/git/commits/boldnew2
Best,
Christian.
next prev parent reply other threads:[~2015-05-19 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <722582475.919095.1431991277969.JavaMail.zimbra@ensimag.grenoble-inp.fr>
2015-05-18 23:23 ` Ensimag students contributing to git Antoine Delaite
2015-05-19 0:50 ` Stefan Beller
2015-05-19 15:39 ` Christian Couder
2015-05-19 15:10 ` Christian Couder
2015-05-19 15:47 ` Christian Couder [this message]
2015-05-20 14:03 ` Remi Galan Alfonso
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='CAP8UFD16vb_-rp7kiATd=XW5FK+P+qkME8hPMku571_PDCQywg@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=antoine.delaite@ensimag.grenoble-inp.fr \
--cc=galanalr@ensimag.grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=lespiner@ensimag.grenoble-inp.fr \
--cc=matthieu.moy@grenoble-inp.fr \
--cc=pagesg@ensimag.grenoble-inp.fr \
--cc=stuberl@ensimag.grenoble-inp.fr \
/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).