From: Christian Couder <email@example.com> To: Stefan Beller <firstname.lastname@example.org>, Johannes Schindelin <Johannes.Schindelin@gmx.de>, git <email@example.com> Subject: Re: Re: Re: Re: GSoC Project | Convert interactive rebase to C Date: Tue, 28 Mar 2017 08:27:24 +0200 Message-ID: <CAP8UFD0i8SV0S7ntpTLBLZF1rFRp-ExdOy=V_-v3eWX98BEqLg@mail.gmail.com> (raw) In-Reply-To: <20170327163108.QoV1fm8z7firstname.lastname@example.org> On Mon, Mar 27, 2017 at 6:31 PM, Pickfire <email@example.com> wrote: > Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote: > >> On Sat, 25 Mar 2017, Ivan Tham wrote: >> >> > Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote: >> > > On Tue, 21 Mar 2017, Ivan Tham wrote: >> > > > Stefan Beller <firstname.lastname@example.org> wrote: >> > > > > On Mon, Mar 20, 2017 at 9:41 AM, Ivan Tham <email@example.com> wrote: >> > > > > >> > > > > > I am interested to work on "Convert interactive rebase to C" >> > > > > >> > > > > +cc Johannes, who recently worked on rebase and the sequencer. >> > > >> > > Glad you are interested! Please note that large parts of the >> > > interactive rebase are already in C now, but there is enough work left >> > > in that corner. >> > >> > Glad to hear that, I would really like to see interactive rebase in C. >> >> Please note that a notable part already made it into C in v2.12.1. There >> are still a few loose ends to tie, of course; it still makes for a great >> head start on your project, methinks. > > Ah, that's great. > > And while I was working on the microproject (shell patterns in user diff), > I can't produce the output of t/t4034-diff-words.sh manually with: I don't think it's a good idea to discuss a microproject in the same thread where a project is discussed. I would suggest to move it in another thread where you describe in more details what you want to do and why, what you expect and what happened, and so on. [...] > That's does not just happens to cpp builtins, it happens to bibtex as well. > Is it that I had missed some configuration since I have tested this on a > few machines? From a very quick look the problem seems related to how test_decode_color() is used or not.
prev parent reply index Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-20 16:41 Ivan Tham 2017-03-20 17:41 ` Stefan Beller 2017-03-21 6:05 ` Ivan Tham 2017-03-23 17:30 ` Johannes Schindelin 2017-03-23 18:19 ` Stefan Beller 2017-03-25 2:17 ` Inaw Tham 2017-03-27 15:11 ` Johannes Schindelin 2017-03-27 16:31 ` Pickfire 2017-03-28 6:27 ` Christian Couder [this message]
Reply instructions: You may reply publically 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='CAP8UFD0i8SV0S7ntpTLBLZF1rFRp-ExdOy=V_-v3eWX98BEqLg@mail.gmail.com' \ --firstname.lastname@example.org \ --cc=Johannes.Schindelin@gmx.de \ --email@example.com \ --firstname.lastname@example.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
email@example.com mailing list mirror (one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox