* [ANNOUNCE] GIT 1.6.1
@ 2008-12-25 6:36 Junio C Hamano
2008-12-25 8:32 ` Christian MICHON
` (3 more replies)
0 siblings, 4 replies; 15+ messages in thread
From: Junio C Hamano @ 2008-12-25 6:36 UTC (permalink / raw)
To: git; +Cc: linux-kernel
The latest feature release GIT 1.6.1 is available at the usual
places:
http://www.kernel.org/pub/software/scm/git/
git-1.6.1.tar.{gz,bz2} (source tarball)
git-htmldocs-1.6.1.tar.{gz,bz2} (preformatted docs)
git-manpages-1.6.1.tar.{gz,bz2} (preformatted docs)
The RPM binary packages for a few architectures are also found in the
vicinity.
RPMS/$arch/git-*-1.6.1-1.fc9.$arch.rpm (RPM)
----------------------------------------------------------------
GIT v1.6.1 Release Notes
========================
Updates since v1.6.0
--------------------
When some commands (e.g. "git log", "git diff") spawn pager internally, we
used to make the pager the parent process of the git command that produces
output. This meant that the exit status of the whole thing comes from the
pager, not the underlying git command. We swapped the order of the
processes around and you will see the exit code from the command from now
on.
(subsystems)
* gitk can call out to git-gui to view "git blame" output; git-gui in turn
can run gitk from its blame view.
* Various git-gui updates including updated translations.
* Various gitweb updates from repo.or.cz installation.
* Updates to emacs bindings.
(portability)
* A few test scripts used nonportable "grep" that did not work well on
some platforms, e.g. Solaris.
* Sample pre-auto-gc script has OS X support.
* Makefile has support for (ancient) FreeBSD 4.9.
(performance)
* Many operations that are lstat(3) heavy can be told to pre-execute
necessary lstat(3) in parallel before their main operations, which
potentially gives much improved performance for cold-cache cases or in
environments with weak metadata caching (e.g. NFS).
* The underlying diff machinery to produce textual output has been
optimized, which would result in faster "git blame" processing.
* Most of the test scripts (but not the ones that try to run servers)
can be run in parallel.
* Bash completion of refnames in a repository with massive number of
refs has been optimized.
* Cygwin port uses native stat/lstat implementations when applicable,
which leads to improved performance.
* "git push" pays attention to alternate repositories to avoid sending
unnecessary objects.
* "git svn" can rebuild an out-of-date rev_map file.
(usability, bells and whistles)
* When you mistype a command name, git helpfully suggests what it guesses
you might have meant to say. help.autocorrect configuration can be set
to a non-zero value to accept the suggestion when git can uniquely
guess.
* The packfile machinery hopefully is more robust when dealing with
corrupt packs if redundant objects involved in the corruption are
available elsewhere.
* "git add -N path..." adds the named paths as an empty blob, so that
subsequent "git diff" will show a diff as if they are creation events.
* "git add" gained a built-in synonym for people who want to say "stage
changes" instead of "add contents to the staging area" which amounts
to the same thing.
* "git apply" learned --include=paths option, similar to the existing
--exclude=paths option.
* "git bisect" is careful about a user mistake and suggests testing of
merge base first when good is not a strict ancestor of bad.
* "git bisect skip" can take a range of commits.
* "git blame" re-encodes the commit metainfo to UTF-8 from i18n.commitEncoding
by default.
* "git check-attr --stdin" can check attributes for multiple paths.
* "git checkout --track origin/hack" used to be a syntax error. It now
DWIMs to create a corresponding local branch "hack", i.e. acts as if you
said "git checkout --track -b hack origin/hack".
* "git checkout --ours/--theirs" can be used to check out one side of a
conflicting merge during conflict resolution.
* "git checkout -m" can be used to recreate the initial conflicted state
during conflict resolution.
* "git cherry-pick" can also utilize rerere for conflict resolution.
* "git clone" learned to be verbose with -v
* "git commit --author=$name" can look up author name from existing
commits.
* output from "git commit" has been reworded in a more concise and yet
more informative way.
* "git count-objects" reports the on-disk footprint for packfiles and
their corresponding idx files.
* "git daemon" learned --max-connections=<count> option.
* "git daemon" exports REMOTE_ADDR to record client address, so that
spawned programs can act differently on it.
* "git describe --tags" favours closer lightweight tags than farther
annotated tags now.
* "git diff" learned to mimic --suppress-blank-empty from GNU diff via a
configuration option.
* "git diff" learned to put more sensible hunk headers for Python,
HTML and ObjC contents.
* "git diff" learned to vary the a/ vs b/ prefix depending on what are
being compared, controlled by diff.mnemonicprefix configuration.
* "git diff" learned --dirstat-by-file to count changed files, not number
of lines, when summarizing the global picture.
* "git diff" learned "textconv" filters --- a binary or hard-to-read
contents can be munged into human readable form and the difference
between the results of the conversion can be viewed (obviously this
cannot produce a patch that can be applied, so this is disabled in
format-patch among other things).
* "--cached" option to "git diff has an easier to remember synonym "--staged",
to ask "what is the difference between the given commit and the
contents staged in the index?"
* "git for-each-ref" learned "refname:short" token that gives an
unambiguously abbreviated refname.
* Auto-numbering of the subject lines is the default for "git
format-patch" now.
* "git grep" learned to accept -z similar to GNU grep.
* "git help" learned to use GIT_MAN_VIEWER environment variable before
using "man" program.
* "git imap-send" can optionally talk SSL.
* "git index-pack" is more careful against disk corruption while
completing a thin pack.
* "git log --check" and "git log --exit-code" passes their underlying diff
status with their exit status code.
* "git log" learned --simplify-merges, a milder variant of --full-history;
"gitk --simplify-merges" is easier to view than with --full-history.
* "git log" learned "--source" to show what ref each commit was reached
from.
* "git log" also learned "--simplify-by-decoration" to show the
birds-eye-view of the topology of the history.
* "git log --pretty=format:" learned "%d" format element that inserts
names of tags that point at the commit.
* "git merge --squash" and "git merge --no-ff" into an unborn branch are
noticed as user errors.
* "git merge -s $strategy" can use a custom built strategy if you have a
command "git-merge-$strategy" on your $PATH.
* "git pull" (and "git fetch") can be told to operate "-v"erbosely or
"-q"uietly.
* "git push" can be told to reject deletion of refs with receive.denyDeletes
configuration.
* "git rebase" honours pre-rebase hook; use --no-verify to bypass it.
* "git rebase -p" uses interactive rebase machinery now to preserve the merges.
* "git reflog expire branch" can be used in place of "git reflog expire
refs/heads/branch".
* "git remote show $remote" lists remote branches one-per-line now.
* "git send-email" can be given revision range instead of files and
maildirs on the command line, and automatically runs format-patch to
generate patches for the given revision range.
* "git submodule foreach" subcommand allows you to iterate over checked
out submodules.
* "git submodule sync" subcommands allows you to update the origin URL
recorded in submodule directories from the toplevel .gitmodules file.
* "git svn branch" can create new branches on the other end.
* "gitweb" can use more saner PATH_INFO based URL.
(internal)
* "git hash-object" learned to lie about the path being hashed, so that
correct gitattributes processing can be done while hashing contents
stored in a temporary file.
* various callers of git-merge-recursive avoid forking it as an external
process.
* Git class defined in "Git.pm" can be subclasses a bit more easily.
* We used to link GNU regex library as a compatibility layer for some
platforms, but it turns out it is not necessary on most of them.
* Some path handling routines used fixed number of buffers used alternately
but depending on the call depth, this arrangement led to hard to track
bugs. This issue is being addressed.
Fixes since v1.6.0
------------------
All of the fixes in v1.6.0.X maintenance series are included in this
release, unless otherwise noted.
* Porcelains implemented as shell scripts were utterly confused when you
entered to a subdirectory of a work tree from sideways, following a
symbolic link (this may need to be backported to older releases later).
* Tracking symbolic links would work better on filesystems whose lstat()
returns incorrect st_size value for them.
* "git add" and "git update-index" incorrectly allowed adding S/F when S
is a tracked symlink that points at a directory D that has a path F in
it (we still need to fix a similar nonsense when S is a submodule and F
is a path in it).
* "git am" after stopping at a broken patch lost --whitespace, -C, -p and
--3way options given from the command line initially.
* "git diff --stdin" used to take two trees on a line and compared them,
but we dropped support for such a use case long time ago. This has
been resurrected.
* "git filter-branch" failed to rewrite a tag name with slashes in it.
* "git http-push" did not understand URI scheme other than opaquelocktoken
when acquiring a lock from the server (this may need to be backported to
older releases later).
* After "git rebase -p" stopped with conflicts while replaying a merge,
"git rebase --continue" did not work (may need to be backported to older
releases).
* "git revert" records relative to which parent a revert was made when
reverting a merge. Together with new documentation that explains issues
around reverting a merge and merging from the updated branch later, this
hopefully will reduce user confusion (this may need to be backported to
older releases later).
* "git rm --cached" used to allow an empty blob that was added earlier to
be removed without --force, even when the file in the work tree has
since been modified.
* "git push --tags --all $there" failed with generic usage message without
telling saying these two options are incompatible.
* "git log --author/--committer" match used to potentially match the
timestamp part, exposing internal implementation detail. Also these did
not work with --fixed-strings match at all.
* "gitweb" did not mark non-ASCII characters imported from external HTML fragments
correctly.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 6:36 [ANNOUNCE] GIT 1.6.1 Junio C Hamano
@ 2008-12-25 8:32 ` Christian MICHON
2008-12-25 10:00 ` bill lam
` (2 subsequent siblings)
3 siblings, 0 replies; 15+ messages in thread
From: Christian MICHON @ 2008-12-25 8:32 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git
On Thu, Dec 25, 2008 at 7:36 AM, Junio C Hamano <gitster@pobox.com> wrote:
> The latest feature release GIT 1.6.1 is available at the usual
> places:
>
a nice christmas gift indeed! thanks for making this release possible.
my best wishes to the list for xmas and incoming 2009!
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 6:36 [ANNOUNCE] GIT 1.6.1 Junio C Hamano
2008-12-25 8:32 ` Christian MICHON
@ 2008-12-25 10:00 ` bill lam
2008-12-25 10:13 ` Junio C Hamano
2008-12-25 18:53 ` Pau Garcia i Quiles
2008-12-25 11:44 ` Heikki Orsila
2008-12-27 10:31 ` [ANNOUNCE] MSYSGIT 1.6.1 Steffen Prohaska
3 siblings, 2 replies; 15+ messages in thread
From: bill lam @ 2008-12-25 10:00 UTC (permalink / raw)
To: git
On ubuntu64 8.10, the NO_UINTMAX_T seems cause some trouble, I have to
comment out the block (in the Makefile),
fdef NO_UINTMAX_T
BASIC_CFLAGS += -Duintmax_t=uint32_t
ndif
to make a successful compilation. Does it happen to me only?
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩282 白居易 後宮詞
淚濕羅巾夢不成 夜深前殿按歌聲 紅顏未老恩先斷 斜倚薰籠坐到明
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 10:00 ` bill lam
@ 2008-12-25 10:13 ` Junio C Hamano
2008-12-25 10:25 ` bill lam
2008-12-25 18:53 ` Pau Garcia i Quiles
1 sibling, 1 reply; 15+ messages in thread
From: Junio C Hamano @ 2008-12-25 10:13 UTC (permalink / raw)
To: bill lam; +Cc: git
bill lam <cbill.lam@gmail.com> writes:
> On ubuntu64 8.10, the NO_UINTMAX_T seems cause some trouble, I have to
> comment out the block (in the Makefile),
>
> fdef NO_UINTMAX_T
> BASIC_CFLAGS += -Duintmax_t=uint32_t
> ndif
>
> to make a successful compilation. Does it happen to me only?
Nobody reported it since that was added about a month and half ago.
Why are you building with NO_UINTMAX_T to begin with? Isn't ubuntu 8.10 a
recent enough platform that ships with modern enough header files that
define ANSI uintmax_t type?
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 10:13 ` Junio C Hamano
@ 2008-12-25 10:25 ` bill lam
2008-12-25 11:42 ` René Scharfe
2008-12-25 18:50 ` Junio C Hamano
0 siblings, 2 replies; 15+ messages in thread
From: bill lam @ 2008-12-25 10:25 UTC (permalink / raw)
To: git
> Why are you building with NO_UINTMAX_T to begin with? Isn't ubuntu 8.10 a
> recent enough platform that ships with modern enough header files that
> define ANSI uintmax_t type?
No, I did not do anything on that,
make clean
./configure --prefix=/usr
make
and this is the error logged.
GIT_VERSION = 1.6.1
* new build flags or prefix
In file included from /usr/include/netinet/in.h:24,
from git-compat-util.h:78,
from builtin.h:4,
from fast-import.c:142:
/usr/include/stdint.h:136: error: conflicting types for ‘uint32_t’
/usr/include/stdint.h:52: error: previous declaration of ‘uint32_t’ was here
fast-import.c: In function ‘parse_progress’:
fast-import.c:2339: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result
make: *** [fast-import.o] Error 1
version of gcc:
gcc (Ubuntu 4.3.2-1ubuntu11) 4.3.2
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩105 杜甫 月夜
今夜鄜州月 閨中只獨看 遙憐小兒女 未解憶長安
香霧雲鬟濕 清輝玉臂寒 何時倚虛幌 雙照淚痕乾
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 10:25 ` bill lam
@ 2008-12-25 11:42 ` René Scharfe
2008-12-25 14:09 ` bill lam
2008-12-25 18:50 ` Junio C Hamano
1 sibling, 1 reply; 15+ messages in thread
From: René Scharfe @ 2008-12-25 11:42 UTC (permalink / raw)
To: bill lam; +Cc: git, Junio C Hamano
bill lam schrieb:
>> Why are you building with NO_UINTMAX_T to begin with? Isn't ubuntu 8.10 a
>> recent enough platform that ships with modern enough header files that
>> define ANSI uintmax_t type?
>
> No, I did not do anything on that,
>
> make clean
> ./configure --prefix=/usr
> make
>
> and this is the error logged.
>
> GIT_VERSION = 1.6.1
> * new build flags or prefix
> In file included from /usr/include/netinet/in.h:24,
> from git-compat-util.h:78,
> from builtin.h:4,
> from fast-import.c:142:
> /usr/include/stdint.h:136: error: conflicting types for ‘uint32_t’
> /usr/include/stdint.h:52: error: previous declaration of ‘uint32_t’ was here
> fast-import.c: In function ‘parse_progress’:
> fast-import.c:2339: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result
> make: *** [fast-import.o] Error 1
>
> version of gcc:
> gcc (Ubuntu 4.3.2-1ubuntu11) 4.3.2
I don't get any error on Ubuntu 8.10 on x86_64 (but several of those
warnings about ignored return values), neither with the tar file nor a
cloned repository (in the former case I had to add a "make configure"
step, though).
Line 52 of /usr/include/stdint.h:
typedef unsigned int uint32_t;
Lines 134-136 of /usr/include/stdint.h:
#if __WORDSIZE == 64
typedef long int intmax_t;
typedef unsigned long int uintmax_t;
If you get to line 136, you probably are on a 64 bit installation, too,
correct?
configure seems to be confused. What happens if you take it out of the
equation, i.e. run the following commands?
$ make distclean
$ make prefix=/usr
René
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 6:36 [ANNOUNCE] GIT 1.6.1 Junio C Hamano
2008-12-25 8:32 ` Christian MICHON
2008-12-25 10:00 ` bill lam
@ 2008-12-25 11:44 ` Heikki Orsila
2008-12-26 1:38 ` Sitaram Chamarty
2008-12-27 1:56 ` Nicolas Pitre
2008-12-27 10:31 ` [ANNOUNCE] MSYSGIT 1.6.1 Steffen Prohaska
3 siblings, 2 replies; 15+ messages in thread
From: Heikki Orsila @ 2008-12-25 11:44 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git, linux-kernel
On Wed, Dec 24, 2008 at 10:36:27PM -0800, Junio C Hamano wrote:
> * The packfile machinery hopefully is more robust when dealing with
> corrupt packs if redundant objects involved in the corruption are
> available elsewhere.
Has anyone written a summary of how Git's redundancy operates?
* What would be the probability for a single bit flip to corrupt the
repository?
* And what is the situation where a single bit flip can not corrupt the
database?
* When (which commands/functions) is error detection done?
Heikki
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 11:42 ` René Scharfe
@ 2008-12-25 14:09 ` bill lam
0 siblings, 0 replies; 15+ messages in thread
From: bill lam @ 2008-12-25 14:09 UTC (permalink / raw)
To: git
On Thu, 25 Dec 2008, René Scharfe wrote:
> configure seems to be confused. What happens if you take it out of the
> equation, i.e. run the following commands?
>
> $ make distclean
> $ make prefix=/usr
Thanks René! I followed your installation, deleted the old configure,
and it compiled successfully,
Happy holidays to everyone on mailing list!
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩104 李白 夜泊牛渚懷古
牛渚西江夜 青天無片雲 登舟望秋月 空憶謝將軍
余亦能高詠 斯人不可聞 明朝挂帆席 楓葉落紛紛
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 10:25 ` bill lam
2008-12-25 11:42 ` René Scharfe
@ 2008-12-25 18:50 ` Junio C Hamano
2008-12-26 14:42 ` bill lam
1 sibling, 1 reply; 15+ messages in thread
From: Junio C Hamano @ 2008-12-25 18:50 UTC (permalink / raw)
To: bill lam; +Cc: git
bill lam <cbill.lam@gmail.com> writes:
>> Why are you building with NO_UINTMAX_T to begin with? Isn't ubuntu 8.10 a
>> recent enough platform that ships with modern enough header files that
>> define ANSI uintmax_t type?
>
> No, I did not do anything on that,
>
> make clean
> ./configure --prefix=/usr
> make
I do not use configure myself (use of configure is entirely optional, and
it is not tested often and core developers do not touch that part very
much --- in a sense, use of autoconf is a second-class citizen in our
build process); it is plausible that it has broken checks for detecting
the need of NO_UINTMAX_T.
Relevant part of configure.ac reads like this:
# Define NO_UINTMAX_T if your platform does not have uintmax_t
AC_CHECK_TYPE(uintmax_t,
[NO_UINTMAX_T=],
[NO_UINTMAX_T=YesPlease],[
#include <inttypes.h>
])
AC_SUBST(NO_UINTMAX_T)
and I do not see anything suspicious there...
Running "./configure --verbose" might leave some clues in config.log; for
me on my primary development box (Debian on x86_64), the relevant part
passes the test (iow, inclusion of inttypes.h does give a working
uintmax_t type) like this:
configure:5709: checking for uintmax_t
configure:5742: cc -c -g -O2 conftest.c >&5
configure:5748: $? = 0
configure:5763: result: yes
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 10:00 ` bill lam
2008-12-25 10:13 ` Junio C Hamano
@ 2008-12-25 18:53 ` Pau Garcia i Quiles
2008-12-26 14:33 ` bill lam
1 sibling, 1 reply; 15+ messages in thread
From: Pau Garcia i Quiles @ 2008-12-25 18:53 UTC (permalink / raw)
To: git
On Thu, Dec 25, 2008 at 11:00 AM, bill lam <cbill.lam@gmail.com> wrote:
> On ubuntu64 8.10, the NO_UINTMAX_T seems cause some trouble, I have to
> comment out the block (in the Makefile),
>
> fdef NO_UINTMAX_T
> BASIC_CFLAGS += -Duintmax_t=uint32_t
> ndif
>
> to make a successful compilation. Does it happen to me only?
Works for me both in Hardy and Intrepid. If you have trouble building
from source, there are binary package for Hardy and Intrepid in my
PPA:
http://launchpad.net/~pgquiles/+archive
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 11:44 ` Heikki Orsila
@ 2008-12-26 1:38 ` Sitaram Chamarty
2008-12-27 1:56 ` Nicolas Pitre
1 sibling, 0 replies; 15+ messages in thread
From: Sitaram Chamarty @ 2008-12-26 1:38 UTC (permalink / raw)
To: git; +Cc: linux-kernel
["Followup-To:" header set to gmane.comp.version-control.git.]
On 2008-12-25, Heikki Orsila <shdl@zakalwe.fi> wrote:
> * What would be the probability for a single bit flip to corrupt the
> repository?
> * And what is the situation where a single bit flip can not corrupt the
> database?
These two questions are not specific to git; whatever
answers apply to sha1 also apply here. Sha1 will always be
strong enough to detect any combination of random errors.
As for deliberate attacks, it is considered strong enough to
resist all but the most computationally intensive attacks
(the kind that require a worldwide effort or maybe NSA type
facilities).
> * When (which commands/functions) is error detection done?
"git fsck --full" will do it of course, but I'm not sure
what other operations also start off or end up doing a
check.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 18:53 ` Pau Garcia i Quiles
@ 2008-12-26 14:33 ` bill lam
0 siblings, 0 replies; 15+ messages in thread
From: bill lam @ 2008-12-26 14:33 UTC (permalink / raw)
To: git
On Thu, 25 Dec 2008, Pau Garcia i Quiles wrote:
> Works for me both in Hardy and Intrepid. If you have trouble building
> from source, there are binary package for Hardy and Intrepid in my
> PPA:
> http://launchpad.net/~pgquiles/+archive
Thanks you head up. No problem now, but I'll bookmark your page.
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩281 劉禹錫 春詞
新妝宜面下朱樓 深鎖春光一院愁 行到中庭數花朵 蜻蜓飛上玉搔頭
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 18:50 ` Junio C Hamano
@ 2008-12-26 14:42 ` bill lam
0 siblings, 0 replies; 15+ messages in thread
From: bill lam @ 2008-12-26 14:42 UTC (permalink / raw)
To: git
On Thu, 25 Dec 2008, Junio C Hamano wrote:
> build process); it is plausible that it has broken checks for detecting
> the need of NO_UINTMAX_T.
>
> Relevant part of configure.ac reads like this:
>
> # Define NO_UINTMAX_T if your platform does not have uintmax_t
> AC_CHECK_TYPE(uintmax_t,
> [NO_UINTMAX_T=],
> [NO_UINTMAX_T=YesPlease],[
> #include <inttypes.h>
> ])
> AC_SUBST(NO_UINTMAX_T)
>
> and I do not see anything suspicious there...
Thanks, I guess the configure is not part of the repository and I use
a legacy configure from earlier version. After I run the make
configure again, it is now ok.
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩093 駱賓王 在獄詠蟬
西路蟬聲唱 南冠客思侵 那堪玄鬢影 來對白頭吟
露重飛難進 風多響易沉 無人信高潔 誰為表予心
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ANNOUNCE] GIT 1.6.1
2008-12-25 11:44 ` Heikki Orsila
2008-12-26 1:38 ` Sitaram Chamarty
@ 2008-12-27 1:56 ` Nicolas Pitre
1 sibling, 0 replies; 15+ messages in thread
From: Nicolas Pitre @ 2008-12-27 1:56 UTC (permalink / raw)
To: Heikki Orsila; +Cc: Junio C Hamano, git, lkml
On Thu, 25 Dec 2008, Heikki Orsila wrote:
> On Wed, Dec 24, 2008 at 10:36:27PM -0800, Junio C Hamano wrote:
> > * The packfile machinery hopefully is more robust when dealing with
> > corrupt packs if redundant objects involved in the corruption are
> > available elsewhere.
>
> Has anyone written a summary of how Git's redundancy operates?
>
> * What would be the probability for a single bit flip to corrupt the
> repository?
This is not something that git itself could answer. The probability
depends on the quality of your hardware. Once that probability has
occurred though, it is clear that your repository is then corrupted as
there is hardly any redundant bits in a git repository.
> * And what is the situation where a single bit flip can not corrupt the
> database?
The database can be resilient against most kind of corruptions if you
have a redundant copy of the affected object. It will still be
corrupted, but git is now able to detect corruptions gracefully and
function correctly with some fallback objects. Those objects must exist
in some other related repository though, and copied over to the affected
repository manually. It's then possible and recommended to "fix" the
corruption simply by repacking the repository at that point.
So there is no magic involved: you need to have some kind of backups,
either using traditional backup solutions, or by simply having your
repository cloned somewhere else. The idea of having a repository fixed
with redundant objects is for those cases where you need to salvage new
work that has no corresponding backup, but although corresponding
objects are not corrupted, they could be delta objects which base is
against old objects which happen to be corrupted.
> * When (which commands/functions) is error detection done?
Error detection is performed all the time. When it's not the more
expensive SHA1 checksum, at least the zlib CRC32 is verified. What the
latest git version does amongst other corruption related things is to
close some small holes where some specific kind of corruptions could
have been undetected and propagated from one pack to another when
repacking.
Nicolas
^ permalink raw reply [flat|nested] 15+ messages in thread
* [ANNOUNCE] MSYSGIT 1.6.1
2008-12-25 6:36 [ANNOUNCE] GIT 1.6.1 Junio C Hamano
` (2 preceding siblings ...)
2008-12-25 11:44 ` Heikki Orsila
@ 2008-12-27 10:31 ` Steffen Prohaska
3 siblings, 0 replies; 15+ messages in thread
From: Steffen Prohaska @ 2008-12-27 10:31 UTC (permalink / raw)
To: Git Mailing List, msysGit; +Cc: Junio C Hamano
On Dec 25, 2008, at 7:36 AM, Junio C Hamano wrote:
> The latest feature release GIT 1.6.1 is available at the usual
> places:
The msysgit installer is available at
http://code.google.com/p/msysgit/downloads
Steffen
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2008-12-27 11:14 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-12-25 6:36 [ANNOUNCE] GIT 1.6.1 Junio C Hamano
2008-12-25 8:32 ` Christian MICHON
2008-12-25 10:00 ` bill lam
2008-12-25 10:13 ` Junio C Hamano
2008-12-25 10:25 ` bill lam
2008-12-25 11:42 ` René Scharfe
2008-12-25 14:09 ` bill lam
2008-12-25 18:50 ` Junio C Hamano
2008-12-26 14:42 ` bill lam
2008-12-25 18:53 ` Pau Garcia i Quiles
2008-12-26 14:33 ` bill lam
2008-12-25 11:44 ` Heikki Orsila
2008-12-26 1:38 ` Sitaram Chamarty
2008-12-27 1:56 ` Nicolas Pitre
2008-12-27 10:31 ` [ANNOUNCE] MSYSGIT 1.6.1 Steffen Prohaska
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).