From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: git-ls-files -m lists the same file multiple times
Date: Wed, 25 Apr 2007 19:52:04 +0100 [thread overview]
Message-ID: <200704251952.07644.andyparkins@gmail.com> (raw)
In-Reply-To: <7v8xcgz4ye.fsf@assigned-by-dhcp.cox.net>
On Wednesday 2007, April 25, Junio C Hamano wrote:
> Andy Parkins <andyparkins@gmail.com> writes:
> > I did a merge, which had conflicts, and then fixed the conflicts.
> > To see what files I'd changed I did git-ls-files -m. This listed
> > the same file multiple times. Some of them twice and some of them
> > three times.
> >
> > I guess that it's showing different stages; but as the list is just
> > filename, there is no way to tell which is which and it is just
> > confusing.
>
> I did not imagine that anybody actually found 'ls-files -m'
> useful, either during a conflicted merge or under the normal
> situation. 'git diff --stat' is usually much more pleasant to
> see.
Definitely. You see I am in the strange position of being able to type
faster than I can think, so typing
git-ls-files -m | xargs git add
Saves me the trouble of engaging my brain :-)
> Use 'ls-files -u' during conflicted merge and be happy.
Great stuff - that's the one I wanted; in fact git-ls-files -m did what
I wanted, because it didn't matter that xargs listed the same file
multiple times.
Thanks
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-04-25 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 9:35 git-ls-files -m lists the same file multiple times Andy Parkins
2007-04-25 18:25 ` Junio C Hamano
2007-04-25 18:52 ` Andy Parkins [this message]
2007-04-25 19:20 ` Junio C Hamano
2007-04-25 20:47 ` Andy Parkins
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=200704251952.07644.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 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.