From: Anand Kumria <wildfire@progsoc.org>
To: git@vger.kernel.org
Subject: Re: selective git-update-index per diff(1) chunks
Date: Fri, 1 Dec 2006 16:45:06 +0000 (UTC) [thread overview]
Message-ID: <ekpm6i$s35$1@sea.gmane.org> (raw)
In-Reply-To: 7v3b7zalsq.fsf@assigned-by-dhcp.cox.net
On Fri, 01 Dec 2006 03:38:13 -0800, Junio C Hamano wrote:
> Peter Baumann <Peter.B.Baumann@stud.informatik.uni-erlangen.de>
> writes:
>
>> I don't think it belongs in the plumbing, the git-update-index but I
>> think something like this would be very usefull.
>>
>> AFAIR darcs has this functionality. It selectively ask for each hunk if
>> it should be commited. This would be awfull to have in git.
>
> I concur, on both counts. My own now-defunct Porcelain had the
> darcs style interactive hunk selection because it felt so
> useful (and sometimes it was).
Is there a good receipe on how to do this? Everytime I do it, I try a
different method; since I'm testing out my understanding of things.
It'd nice to have some of these "advanced receipes" that people often do
noted down somewhere.
Sometimes I feel git is kind of like the Emacs of VCS ... there is always
more to learn, even when you think you have a good handle on things.
Cheers,
Anand
next prev parent reply other threads:[~2006-12-01 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 11:23 selective git-update-index per diff(1) chunks Alexey Dobriyan
2006-12-01 11:33 ` Peter Baumann
2006-12-01 11:38 ` Junio C Hamano
2006-12-01 16:45 ` Anand Kumria [this message]
2006-12-01 19:42 ` Johannes Schindelin
2006-12-02 21:08 ` Sam Vilain
2006-12-01 16:06 ` Linus Torvalds
2006-12-04 17:33 ` Sven Verdoolaege
2006-12-04 18:05 ` Jakub Narebski
[not found] ` <20061204202102.GH940MdfPADPa@greensroom.kotnet.org>
2006-12-04 20:46 ` Jakub Narebski
2006-12-04 21:51 ` Sven Verdoolaege
2006-12-04 22:35 ` Jakub Narebski
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='ekpm6i$s35$1@sea.gmane.org' \
--to=wildfire@progsoc.org \
--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).