From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: [PATCH 0/5] git-add/git-rm updates
Date: Mon, 25 Dec 2006 03:09:22 -0800 [thread overview]
Message-ID: <7vr6uomdul.fsf@assigned-by-dhcp.cox.net> (raw)
This series futzes with a pair of functions in dir.c machinery
and enhances git-add and git-rm command.
[PATCH 1/5] match_pathspec() -- return how well the spec matched
The function match_pathspec() takes the pathspec given from the
command line and tells if a given name matches it. This
enhances its return value so that the command can tell how well
the name matches. Earlier, the caller could not tell if matched
pathspec was exactly the same as the name, was a fileglob that
matched the name, or was a leading directory.
[PATCH 2/5] git-rm: update to saner semantics
[PATCH 3/5] t3600: update the test for updated git rm
This updates git-rm to saner semantics Linus suggested on the
list earlier, and updates the tests. When a path is removed, it
is removed both from the working tree and from the index. As a
safety measure, the path is required to be cache-clean, and also
must match the HEAD (unless it is before the initial commit on
the branch).
[PATCH 4/5] read_directory: show_both option.
The function read_directory() is the workhorse to traverse
working tree while taking '.gitignore' into account. This
updates the function to allow callers that are interested in
both ignored and non-ignored paths to get both paths so that it
can do its own filtering on the result.
[PATCH 5/5] git-add: add ignored files when asked explicitly.
One thing many people found confusing about git-add was that a
file whose name matches an ignored pattern could not be added.
This is an RFC fix for the problem.
reply other threads:[~2006-12-25 11:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7vr6uomdul.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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