Git development
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: Pedro Melo <melo@simplicidade.org>
Cc: William Morgan <wmorgan-git@masanjin.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git-walkthrough-add script
Date: Sat, 5 Jan 2008 02:00:11 +0100	[thread overview]
Message-ID: <20080105010011.GV29972@genesis.frugalware.org> (raw)
In-Reply-To: <2CC98B8C-CBB1-4C26-8C94-B152A4D02DDC@simplicidade.org>

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

On Fri, Jan 04, 2008 at 11:26:41PM +0000, Pedro Melo <melo@simplicidade.org> wrote:
> Maybe I'm doing something wrong, but comparing git-add -p with your script, 
> git-add -p is more darcs'ish. With git-add, if I have several changes in 
> the same file, I get to choose per hunk.

hm, if you want a darcs-like record interface.. darcs record asks you if
you want to include a newly added file in a commit or not,
git-walkthrough-add won't do so :s

you might want to have a look at dg record
(http://git.frugalware.org/repos/pacman-tools/darcs-git.py) which does
this for you.

- VMiklos

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-01-05  1:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04  6:14 git-walkthrough-add script William Morgan
2008-01-04  7:26 ` Jeff King
2008-01-04 18:31   ` William Morgan
2008-01-04 21:07     ` Jeff King
2008-01-05  2:37       ` William Morgan
2008-01-05  2:50         ` Junio C Hamano
2008-01-05  2:55           ` Junio C Hamano
2008-01-05  3:02             ` William Morgan
2008-01-05  4:08           ` Pedro Melo
2008-01-04 23:26 ` Pedro Melo
2008-01-04 23:28   ` Junio C Hamano
2008-01-05  0:02   ` William Morgan
2008-01-05  0:17     ` Pedro Melo
2008-01-05  1:00   ` Miklos Vajna [this message]
2008-01-05  2:54     ` William Morgan
2008-01-05  3:43       ` Jeff King

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=20080105010011.GV29972@genesis.frugalware.org \
    --to=vmiklos@frugalware.org \
    --cc=git@vger.kernel.org \
    --cc=melo@simplicidade.org \
    --cc=wmorgan-git@masanjin.net \
    /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