All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: selective git-update-index per diff(1) chunks
Date: Mon, 04 Dec 2006 19:05:04 +0100	[thread overview]
Message-ID: <el1nsi$vat$1@sea.gmane.org> (raw)
In-Reply-To: 20061204173318.GG940MdfPADPa@greensroom.kotnet.org

Sven Verdoolaege wrote:

> On Fri, Dec 01, 2006 at 02:23:14PM +0300, Alexey Dobriyan wrote:
>> Has anyone thought about aggregating this into git-update-index or
>> somewhere?
>> 
>>    git-update-index -C1,3    #chunks 1, 3
>>    git commit
>>    git-update-index -C1,3    # chunks 2,5 in original numbering
>>    git commit
>> 
>> Relying on diff(1) definition of chunks is sorta hacky, though... I admit 
>> it.
> 
> Paul Mackerras modified his dirdiff tool to do something like this.
> I have a couple of patches on top of his version from way back at
> http://www.liacs.nl/~sverdool/gitweb.cgi?p=dirdiff.git;a=summary
> 
> I don't know if he has continued working on this.

If this has support for git, could you add it to GitWiki:
  http://git.or.cz/gitwiki/InterfacesFrontendsAndTools
And perhaps also update related page
  http://git.or.cz/gitwiki/InterfacesFrontendsAndToolsWishlist

Thanks in advance.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


  reply	other threads:[~2006-12-04 18:03 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
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 [this message]
     [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='el1nsi$vat$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.