From: Johannes Sixt <j.sixt@viscovery.net>
To: Wincent Colaiuta <win@wincent.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Hunk splitting in "git gui"
Date: Fri, 28 Dec 2007 13:38:13 +0100 [thread overview]
Message-ID: <4774EE35.10905@viscovery.net> (raw)
In-Reply-To: <3F129AD6-EA27-4584-B5C8-2866964AB93E@wincent.com>
Wincent Colaiuta schrieb:
> I'd use "git gui" a lot more if I could split hunks in it (like you can
> in "git add --interactive").
>
> Problem is, I have zero knowledge of Tcl/Tk. Can someone who has
> knowledge of this offer an opinion on whether this would be a feasible
> project for a beginner? I'm willing to have a shot at it, but before I
> embark on this I'd like to know if others consider it useful and doable!
Look at the sub-thread that started here:
http://article.gmane.org/gmane.comp.version-control.git/68091
Be sure not to skip the explanation why --unidiff-zero is dangerous.
-- Hannes
next prev parent reply other threads:[~2007-12-28 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 12:26 Hunk splitting in "git gui" Wincent Colaiuta
2007-12-28 12:38 ` Johannes Sixt [this message]
2007-12-28 15:37 ` Wincent Colaiuta
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=4774EE35.10905@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=win@wincent.com \
/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