2012-10-31 12:19:55 by Aleksej Saushev | Files touched by this commit (1460) |
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
|
2012-10-28 02:17:09 by Christos Zoulas | Files touched by this commit (2) |
Log message:
undo previous
|
2012-10-27 22:26:17 by Christos Zoulas | Files touched by this commit (2) |
Log message:
kind of hard to use http repositories without the http helper.
|
2012-10-06 20:28:13 by Adam Ciarcinski | Files touched by this commit (5) | |
Log message:
Fixes since v1.7.12.1
---------------------
* When "git am" is fed an input that has multiple "Content-type: \
..."
header, it did not grok charset= attribute correctly.
* Even during a conflicted merge, "git blame $path" always meant to
blame uncommitted changes to the "working tree" version; make it
more useful by showing cleanly merged parts as coming from the other
branch that is being merged.
* "git blame MAKEFILE" run in a history that has "Makefile" \
but not
"MAKEFILE" should say "No such file MAKEFILE in HEAD", but got
confused on a case insensitive filesystem and failed to do so.
* "git fetch --all", when passed "--no-tags", did not honor the
"--no-tags" option while fetching from individual remotes (the same
issue existed with "--tags", but combination "--all \
--tags" makes
much less sense than "--all --no-tags").
* "git log/diff/format-patch --stat" showed the "N line(s) \
added"
comment in user's locale and caused careless submitters to send
patches with such a line in them to projects whose project language
is not their language, mildly irritating others. Localization to
the line has been disabled for now.
* "git log --all-match --grep=A --grep=B" ought to show commits that
mention both A and B, but when these three options are used with
--author or --committer, it showed commits that mention either A or
B (or both) instead.
* The subcommand to remove the definition of a remote in "git remote"
was named "rm" even though all other subcommands were spelled out.
Introduce "git remote remove" to remove confusion, and keep \
"rm" as
a backward compatible synonym.
Also contains a handful of documentation updates.
|
2012-10-03 23:59:10 by Thomas Klausner | Files touched by this commit (2798) |
Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.
I hope that's all of them.
|
2012-09-25 16:22:48 by Takahiro Kambe | Files touched by this commit (2) |
Log message:
Add workaround for scmgit-doc build problem.
|
2012-09-16 23:50:16 by Aleksey Cheusov | Files touched by this commit (4) |
Log message:
Remove option scmgit-gui from devel/scmgit-base (++pkgrevision). Separate
"gitk" into individual package devel/scmgit-gitk. Approved by wiz@.
Tested on RHEL.
|
2012-09-04 14:17:12 by Adam Ciarcinski | Files touched by this commit (6) | |
Log message:
Changes 1.7.12:
UI, Workflows & Features
* Git can be told to normalize pathnames it read from readdir(3) and
all arguments it got from the command line into precomposed UTF-8
(assuming that they come as decomposed UTF-8), in order to work
around issues on Mac OS.
I think there still are other places that need conversion
(e.g. paths that are read from stdin for some commands), but this
should be a good first step in the right direction.
* Per-user $HOME/.gitconfig file can optionally be stored in
$HOME/.config/git/config instead, which is in line with XDG.
* The value of core.attributesfile and core.excludesfile default to
$HOME/.config/git/attributes and $HOME/.config/git/ignore respectively
when these files exist.
* Logic to disambiguate abbreviated object names have been taught to
take advantage of object types that are expected in the context,
e.g. XXXXXX in the "git describe" output v1.2.3-gXXXXXX must be a
commit object, not a blob nor a tree. This will help us prolong
the lifetime of abbreviated object names.
* "git apply" learned to wiggle the base version and perform three-way
merge when a patch does not exactly apply to the version you have.
* Scripted Porcelain writers now have access to the credential API via
the "git credential" plumbing command.
* "git help" used to always default to "man" format even on \
platforms
where "man" viewer is not widely available.
* "git clone --local $path" started its life as an experiment to
optionally use link/copy when cloning a repository on the disk, but
we didn't deprecate it after we made the option a no-op to always
use the optimization. The command learned "--no-local" option to
turn this off, as a more explicit alternative over use of file://
URL.
* "git fetch" and friends used to say "remote side hung up
unexpectedly" when they failed to get response they expect from the
other side, but one common reason why they don't get expected
response is that the remote repository does not exist or cannot be
read. The error message in this case was updated to give better
hints to the user.
* "git help -w $cmd" can show HTML version of documentation for
"git-$cmd" by setting help.htmlpath to somewhere other than the
default location where the build procedure installs them locally;
the variable can even point at a http:// URL.
* "git rebase [-i] --root $tip" can now be used to rewrite all the
history leading to "$tip" down to the root commit.
* "git rebase -i" learned "-x <cmd>" to insert \
"exec <cmd>" after
each commit in the resulting history.
* "git status" gives finer classification to various states of paths
in conflicted state and offer advice messages in its output.
* "git submodule" learned to deal with nested submodule structure
where a module is contained within a module whose origin is
specified as a relative URL to its superproject's origin.
* A rather heavy-ish "git completion" script has been split to create
a separate "git prompting" script, to help lazy-autoloading of the
completion part while making prompting part always available.
* "gitweb" pays attention to various forms of credits that are
similar to "Signed-off-by:" lines in the commit objects and
highlights them accordingly.
|
2012-07-23 22:16:04 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
Changes 1.7.11.3
* The error message from "git push $there :bogo" (and its equivalent
"git push $there --delete bogo") mentioned that we tried and failed
to guess what ref is being deleted based on the LHS of the refspec,
which we don't.
* A handful of files and directories we create had tighter than
necessary permission bits when the user wanted to have group
writability (e.g. by setting "umask 002").
* "commit --amend" used to refuse amending a commit with an empty log
message, with or without "--allow-empty-message".
* "git commit --amend --only --" was meant to allow "Clever" \
people to
rewrite the commit message without making any change even when they
have already changes for the next commit added to their index, but
it never worked as advertised since it was introduced in 1.3.0 era.
* Even though the index can record pathnames longer than 1<<12 bytes,
in some places we were not comparing them in full, potentially
replacing index entries instead of adding.
* "git show"'s auto-walking behaviour was an unreliable and
unpredictable hack; it now behaves just like "git log" does when it
walks.
* "git diff", "git status" and anything that internally uses the
comparison machinery was utterly broken when the difference
involved a file with "-" as its name. This was due to the way "git
diff --no-index" was incorrectly bolted on to the system, making
any comparison that involves a file "-" at the root level
incorrectly read from the standard input.
* We did not have test to make sure "git rebase" without extra options
filters out an empty commit in the original history.
* "git fast-export" produced an input stream for fast-import without
properly quoting pathnames when they contain SPs in them.
* "git checkout --detach", when you are still on an unborn branch,
should be forbidden, but it wasn't.
* Some implementations of Perl terminates "lines" with CRLF even when
the script is operating on just a sequence of bytes. Make sure to
use "$PERL_PATH", the version of Perl the user told Git to use, in
our tests to avoid unnecessary breakages in tests.
Also contains minor typofixes and documentation updates.
|
2012-07-18 14:09:57 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
Changes 1.7.11.2:
* On Cygwin, the platform pread(2) is not thread safe, just like our
own compat/ emulation, and cannot be used in the index-pack
program. Makefile variable NO_THREAD_SAFE_PREAD can be defined to
avoid use of this function in a threaded program.
* "git add" allows adding a regular file to the path where a
submodule used to exist, but "git update-index" does not allow an
equivalent operation to Porcelain writers.
* "git archive" incorrectly computed the header checksum; the symptom
was observed only when using pathnames with hi-bit set.
* "git blame" did not try to make sure that the abbreviated commit
object names in its output are unique.
* Running "git bundle verify" on a bundle that records a complete
history said "it requires these 0 commits".
* "git clone --single-branch" to clone a single branch did not limit
the cloning to the specified branch.
* "git diff --no-index" did not correctly handle relative paths and
did not correctly give exit codes when run under "--quiet" option.
* "git diff --no-index" did not work with pagers correctly.
* "git diff COPYING HEAD:COPYING" gave a nonsense error message that
claimed that the treeish HEAD did not have COPYING in it.
* When "git log" gets "--simplify-merges/by-decoration" \
together with
"--first-parent", the combination of these options makes the
simplification logic to use in-core commit objects that haven't
been examined for relevance, either producing incorrect result or
taking too long to produce any output. Teach the simplification
logic to ignore commits that the first-parent traversal logic
ignored when both are in effect to work around the issue.
* "git ls-files --exclude=t -i" did not consider anything under t/ as
excluded, as it did not pay attention to exclusion of leading paths
while walking the index. Other two users of excluded() are also
updated.
* "git request-pull $url dev" when the tip of "dev" branch \
was tagged
with "ext4-for-linus" used the contents from the tag in the output
but still asked the "dev" branch to be pulled, not the tag.
Also contains minor typofixes and documentation updates.
|