From: "Clément Poulain" <clement.poulain@ensimag.imag.fr>
To: git@vger.kernel.org
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Axel Bonnet <axel.bonnet@ensimag.imag.fr>,
Diane Gasselin <diane.gasselin@ensimag.imag.fr>
Subject: Re: Getting Ensimag students to work on Git for a few weeks
Date: Sat, 29 May 2010 00:53:25 +0200 [thread overview]
Message-ID: <4C004965.6040802@ensimag.imag.fr> (raw)
In-Reply-To: <20100522112652.GA15328@localhost>
Le 22/05/2010 13:26, Clemens Buchacher a écrit :
> On Fri, May 21, 2010 at 07:44:42PM +0200, Matthieu Moy wrote:
>
>
>> As a first exercice, they'll try to add textconv support
>> to git-blame. The next tasks are undecided yet (but advices are
>> welcome).
>>
> Just FYI, there is a patch pending to add textconv support to git-gui.
>
> http://mid.gmane.org/20100415193944.GA5848@localhost
>
> Clemens
>
Thank you for this information.
As we are about to finish to add textconv support to git-blame, we'll
now look to add it to git-gui blame.
We wonder what would be the best choice between add a second option "Use
Textconv For Blames", or transform the existing one (introduced by the
patch above) into "Use Textconv For Diffs and Blames" (so the user
wouldn't have the choice to use textconv only for Diffs or only for
Blames; is it really usefull ?).
Your advice is welcome !
Thanks,
Clément
prev parent reply other threads:[~2010-05-28 22:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 10:12 Getting Ensimag students to work on Git for a few weeks Matthieu Moy
2009-10-27 13:59 ` Johannes Schindelin
2009-10-27 15:54 ` Matthieu Moy
2009-10-27 14:44 ` Clemens Buchacher
2009-10-27 16:39 ` Matthieu Moy
2009-10-28 22:41 ` Jakub Narebski
2009-10-27 15:47 ` Hervé Cauwelier
2009-10-27 16:32 ` Matthieu Moy
2010-05-21 17:44 ` Matthieu Moy
2010-05-22 11:26 ` Clemens Buchacher
2010-05-28 22:53 ` Clément Poulain [this message]
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=4C004965.6040802@ensimag.imag.fr \
--to=clement.poulain@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=axel.bonnet@ensimag.imag.fr \
--cc=diane.gasselin@ensimag.imag.fr \
--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.
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).