when HEAD points nowhere
John Keeping (1):
git-cvsimport.txt: cvsps-2 is deprecated
Jonathan Nieder (2):
ident: do not drop username when reading from /etc/mailname
Makefile: explicitly set target name for autogenerated dependencies
Junio C Hamano (17):
Which merge_file(
git-for-each-ref.txt: 'raw' is a supported date format
Jonathan Nieder (1):
contrib/vim: simplify instructions for old vim support
Junio C Hamano (2):
Start preparing for 1.8.1.2
Git 1.8.1.2
Marc Khouzam (1):
Prevent space after directories in tcs
to do the same for --htmldir.
(merge 55d9bf0 ct/autoconf-htmldir later to maint).
* A change made on v1.8.1.x maintenance track had a nasty regression
to break the build when autoconf is used.
(merge 7f1b697 jn/less-reconfigure later to maint).
* We have been carrying a translated and lon
Matthieu Moy writes:
> Junio C Hamano writes:
>
>> Git v1.8.2 Release Notes (draft)
>>
>>
>> Backward compatibility notes
>>
>>
>> In the upcoming major release (tentatively called 1.8.2),
Junio C Hamano writes:
>> I don't understand: wasn't this supposed to happen in Git 2.0? Did you
>> mean "In the upcoming major release (tentatively called *2.0*)"?
>
> Thanks. I am not sure what I was thinking. Perhaps when we started
> this cycle we
tificate matched the host it thought it was talking to.
Also contains various documentation fixes.
Changes since v1.8.1.3 are as follows:
Junio C Hamano (2):
imap-send: move #ifdef around
Git 1.8.1.4
Matthieu Mo
Linus Torvalds writes:
> One is simple:
>
> git config alias.sync="pull --ff-only"
Heh, I just wrote that myself after reading the early part of this
message ;-)
> which works fine, but forces submaintainers to be careful when doing
> things like this, and using a special command to do back
Junio C Hamano writes:
> Then under the "--no-ff activates the magic" rule:
>
> git merge v3.9-rc2
>
> will fast-forward, but this
>
> git merge --no-ff v3.9-rc2
>
> creates a real merge with the "mergetag" signature block. The one
&g
Stephen Rothwell writes:
> I wonder if "git merge v3.9-rc2^{}" should work.
With less typing, "git merge v3.9-rc2^0", is the more traditional
way, but "git merge v3.9-rc2^{}" should also work.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
Theodore Ts'o writes:
> What if we added the ability to do something like this:
>
> [remote "origin"]
> url =
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> fetch = +refs/heads/master:refs/heads/master
> mergeoptions = --ff-only
>
> This would be an an
Linus Torvalds writes:
> - I do think that we might want a "--no-signatures" for the specific
> case of merging signed tags without actually taking the signature
> (because it's a "upstream" repo). The "--ff-only" thing is *too*
> strict. Sometimes you really do want to merge in new code, disall
Linus Torvalds writes:
> That said, adding the signature from an upstream tag doesn't really
> seem to be hugely useful. I'm not seeing much of an upside, in other
> words. I'd *expect* that people would pick up upstream tags
> regardless, no?
Yes, their "git fetch" will auto-follow, but mergeta
Theodore Ts'o writes:
> On Tue, Mar 12, 2013 at 02:30:04PM -0700, Junio C Hamano wrote:
>> Theodore Ts'o writes:
>>
>> > [remote "origin"]
>> >url =
>> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linu
can configure this fail for the current user (e.g. you
need to be in the cvsadmin group on NetBSD 6.0).
* t9020 and t9810 had a few non-portable shell script construct.
* Scripts to test bash completion was inherently flaky as it was
affected by whatever random things the user may have on $PATH.
ciabot scripts.
Make the ciabot scripts completely self-configuring in the normal case.
Heiko Voigt (2):
Let submodule command exit with error status if path does not exist
Documentation/CodingGuidelines: spell out more shell guidelines
Jay Soffian (1):
gitweb: URL-decode $
Takashi Iwai writes:
>> I can't reproduce here. What is your exact request-pull invocation?
This question was not answerd. Did you ask request-pull to ask for
a branch to be pulled, or did you ask it to ask for the tag to be
pulled?
If the former, I would have say it is a pebcak. Linus asked
The latest feature release GIT 1.5.4 is available at the usual
places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.4.tar.{gz,bz2}(tarball)
git-htmldocs-1.5.4.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.4.tar.{gz,bz2} (prefo
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Wed, 13 Feb 2008, Linus Torvalds wrote:
>>
>> So in that sense, I think both MAINTAINERS and the deprecation schedule
>> are totally uninteresting. Yes, they have merge conflicts. But those merge
>> conflicts are really really easy to handle.
>
>
hanges since v1.7.11.3 are as follows:
Jeff King (3):
diff: test precedence of external diff drivers
advice: pass varargs to strbuf_vaddf, not strbuf_addf
commit: document the temporary commit message file
Jens Lehmann (1):
submodules: don't stumble over symbolic links when
A release candidate Git v1.7.12-rc1 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
34f04ef64fd60bec32388afe27cc4e447ca55229 git-1.7.12.rc1.tar.gz
88a97012fd1454190e8eb49114
receive-pack: redirect unpack-objects stdout to /dev/null
receive-pack: send pack-processing stderr over sideband
receive-pack: drop "n/a" on unpacker errors
Junio C Hamano (3):
git blame: document that it always follows origin across whole-file
renames
Start prepari
its prompt,
tempting the user to say "y". But the response was taken as "No,
please use 'y' as the e-mail address instead", which is most
certainly not what the user meant.
* "git show --format='%ci'" did not give the timestamp correctly for
A release candidate preview, Git v1.8.1-rc0, is now available for
testing at the usual places.
This cycle has been a bit slow (perhaps because it had a major US
holiday to slow people down) but we seem to have managed to apply
reasonably large number of usability improvement changes, with a
handfu
Ramsay Jones writes:
> I fetch git from 'git://git.kernel.org/pub/scm/git/git.git' which has
> commit ee26a6e2 ("Git 1.8.1-rc0", 03-12-2012), but is missing the v1.8.1-rc0
> tag. Is this just an oversight ...
Thanks for letting me know; forgot to push out the tag.
--
To unsubscribe from this l
kefile: Allow custom XMLTO binary
Dylan Alex Simon (1):
gitweb.cgi: fix "comitter_tz" typo in feed
Jeff King (1):
http: fix segfault in handle_curl_result
Junio C Hamano (6):
merge: teach -Xours/-Xtheirs to binary ll-merge driver
attr: "binary" attribu
d-email" gives was error prone. It
asked "What e-mail address do you want to use?" with the address it
guessed (correctly) the user would want to use in its prompt,
tempting the user to say "y". But the response was taken as "No,
please use 'y'
eant.
* "git show --format='%ci'" did not give the timestamp correctly for
commits created without human readable name on the "committer" line.
* "git show --quiet" ought to be a synonym for "git show -s", but
wasn't.
* "git s
content in the "git diff --stat" output.
* When "--stat-count" hides a diffstat for binary contents, the total
number of added and removed lines at the bottom was computed
incorrectly.
* When "--stat-count" hides a diffstat for unmerged paths, the tot
ilt
Johan Herland (2):
t1400-update-ref: Add test verifying bug with symrefs in delete_ref()
Fix failure to delete a packed ref through a symref
Junio C Hamano (13):
reencode_string(): introduce and use same_encoding()
test: add failing tests for "diff --stat" to t40
oken entry for Martin Langhoff
.mailmap: normalize emails for Jeff King
.mailmap: normalize emails for Linus Torvalds
contrib: update stats/mailmap script
John Keeping (1):
Documentation: don't link to example mail addresses
Junio C Hamano (6):
fetch --tags: cla
notably, mailinfo (which is used by "git am") lacked this support.
* We failed to mention a file without any content change but whose
permission bit was modified, or (worse yet) a new file without any
content in the "git diff --stat" output.
* When "--stat-count&quo
ectly.
* "diff --shortstat" miscounted the total number of affected files
when there were unmerged paths.
* "update-ref -d --deref SYM" to delete a ref through a symbolic ref
that points to it did not remove it correctly.
---
The latest maintenance release Git v1.8.3.1 is now available at the
usual places.
This is primarily to push out fixes to two regressions that seem to
affect many people, namely, the ".gitignore !directory" bug and the
"daemon cannot read from $HOME owned by root" bug.
The release tarballs are fou
The latest maintenance release Git v1.8.3.2 is now available at the
usual places. It contains fixes that have already been applied to
the 'master' branch for 1.8.4.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
4a6585dd81
iff -c -p" was not showing a deleted line from a hunk when
another hunk immediately begins where the earlier one ends.
* "git log --ancestry-path A...B" did not work as expected, as it did
not pay attention to the fact that the merge base between A and B
was the botto
remove useless indentation
sequencer: avoid leaking message buffer when refusing to create an empty
commit
Filipe Cabecinhas (1):
compate/clipped-write.c: large write(2) fails on Mac OS X/XNU
Fredrik Gustafsson (1):
handle multibyte characters in name
Jeff King (1):
pull:
with
their CommonCrypto, not with OpenSSL.
* "git clone foo/bar:baz" cannot be a request to clone from a remote
over git-over-ssh specified in the scp style. This case is now
detected and clones from a local repository at "foo/bar:baz".
* When $HOME is misconfigured
The latest feature release Git v1.8.4 is now available at the usual
places. It contains 870+ changes from ~100 contributors (among
which 33 people are new) since v1.8.3.
We will have two more releases til the end of this year; the release
after that could be Git 2.0.
The release tarballs are fou
not pay attention to the fact that the merge base between A and B
was the bottom of the range being specified.
* Mac OS X does not like to write(2) more than INT_MAX number of
bytes; work it around by chopping write(2) into smaller pieces.
* Newer MacOS X encourages the programs to compile and
NKS prerequisite
t3100: use test_ln_s_add to remove SYMLINKS prerequisite
t3509, t4023, t4114: use test_ln_s_add to remove SYMLINKS prerequisite
t6035: use test_ln_s_add to remove SYMLINKS prerequisite
t4011: remove SYMLINKS prerequisite
Junio C Hamano (7):
fetch-opt
A release candidate preview Git v1.8.4-rc0 is now available for
testing at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
8e0d93653633fcaffc829f607bd8c1077a855c1d git-1.8.4.rc0.tar.gz
1e2b18ea855b3e06ab2e
cestry-path A...B" did not work as expected, as it did
not pay attention to the fact that the merge base between A and B
was the bottom of the range being specified.
* Mac OS X does not like to write(2) more than INT_MAX number of
bytes; work it around by chopping write(2) into small
(1):
Add utf8_fprintf helper that returns correct number of columns
John Keeping (3):
Rename {git- => git}remote-helpers.txt
builtin/apply: tighten (dis)similarity index parsing
t4038: add tests for "diff --cc --raw "
Junio C Hamano (7):
doc: ment
runs "cvs init" on a directory that already exists, but a
platform can configure this fail for the current user (e.g. you
need to be in the cvsadmin group on NetBSD 6.0).
* t9020 and t9810 had a few non-portable shell script construct.
* Scripts to test bash completion was inherently flaky as it was
affected by whatever random things the
en diffing
Felipe Contreras (25):
remote-bzr: cleanup CustomTree
remote-bzr: delay blob fetching until the very end
remote-bzr: fix order of locking in CustomTree
remote-bzr: always try to update the worktree
remote-bzr: add support to push merges
remote-bzr: fixes
ttern without trailing slash matches a directory
Johannes Sixt (1):
t2003: work around path mangling issue on Windows
John Keeping (3):
t2003: modernize style
entry: fix filter lookup
merge-tree: fix typo in merge-tree.c::unresolved
Joshua Clayton (1):
Git.pm: fix
ect_entry list
fast-import: use pointer-to-pointer to keep list tail
drop some obsolete "x = x" compiler warning hacks
transport: drop "int cmp = cmp" hack
run-command: always set failed_errno in start_command
fast-import: clarify "inline&quo
tags was not done correctly when not in C
or en/US locale.
* Some platforms and users spell UTF-8 differently; retry with the
most official "UTF-8" when the system does not understand the
user-supplied encoding name that is a common alternative
spelling of UTF-8.
* When ex
complete: zsh: use zsh completion for the main cmd
completion: zsh: don't override suffix on _detault
transport-helper: trivial style cleanup
John Keeping (1):
t/Makefile: remove smoke test targets
Jonathan Nieder (1):
glossary: a revision is just a commit
Ju
not segfault if not all stages are present
t6200: avoid path mangling issue on Windows
John Keeping (5):
diffcore-break: don't divide by zero
bisect: avoid signed integer overflow
git-merge(1): document diff-algorithm option to merge-recursive
diff: allow unstuck
A release candidate preview Git v1.8.3-rc0 is now available for
testing at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
f0b0b415f0c693865895c1918859b12c4a7d5b17 git-1.8.3.rc0.tar.gz
089efc61b3d45504cb53
Michael Haggerty writes:
> On 04/27/2013 04:24 AM, shawn wilson wrote:
>> On Fri, Apr 26, 2013 at 8:22 PM, Junio C Hamano wrote:
>>
>>> * There was no good way to ask "I have a random string that came from
>>>outside world. I want to turn it into a
used, "zip" output recorded an incorrect
size of the file.
* "git am $maildir/" applied messages in an unexpected order; sort
filenames read from the maildir/ in a way that is more likely to
sort the messages in the order the writing MUA meant to, by sorting
nume
The latest feature release Git v1.8.3 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
bfb88c182daeed5601ba860d785ac813433f55f1 git-1.8.3.tar.gz
92cc8ae5f4c1db2e7751ad0dc9c3227ca31080aa
runs "cvs init" on a directory that already exists, but a
platform can configure this fail for the current user (e.g. you
need to be in the cvsadmin group on NetBSD 6.0).
* t9020 and t9810 had a few non-portable shell script construct.
* Scripts to test bash completion was inherently flaky as it was
affected by whatever random things
A maintenance release Git v1.7.11.7 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
30c7aafaa31002ca52bc45dbd0908e63b00015dd git-1.7.11.7.tar.gz
bdcd5009498bc961757915dae30f5fefd6435c59
config: warn on inaccessible files
gitignore: report access errors of exclude files
attr: warn on inaccessible attribute files
t5550: put auth-required repo in auth/dumb
t5550: factor out http auth setup
t/lib-httpd: only route auth/dumb to dumb repos
t/lib-httpd: recogn
i18n: Rewrite gettext messages start with dash
rebase: remove obsolete and unused LONG_USAGE which breaks xgettext
i18n: am: mark more strings for translation
Remove dead code which contains bad gettext block
i18n: merge-recursive: mark strings for translation
l10n: Upda
ial commit
Johannes Schindelin (3):
bisect: allow starting with a detached HEAD
Document that the default of branch.autosetupmerge is true
bisect: use verbatim commit subject in the bisect log
Johannes Sixt (1):
upload-pack: Initialize the exec-path.
Jonas Fonseca (1):
Linus Torvalds <[EMAIL PROTECTED]> writes:
> So I'd be happier with warnings about deep indentation (but how do you
> count it? Will people then try to fake things out by using 4-space indents
> and then "deep" indentations will look like just a couple of tabs?) and
> against complex expression
nd object flags
Jonathan Nieder (4):
block-sha1: avoid pointer conversion that violates alignment constraints
block-sha1: put expanded macro parameters in parentheses
Makefile: fix location of listing produced by "make subdir/foo.s"
Makefile: BLK_SHA1 does not req
RK_TREE was used to access it.
* "git commit --amend" let the user edit the log message and then died
when the human-readable committer name was given insufficiently by
getpwent(3).
Changes since v1.7.12-rc2 are as f
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Fri, 8 Feb 2008, Jonathan Corbet wrote:
>> +
>> +These tags are:
>> +
>> +From: The original author of the patch. This tag will ensure
>> +that credit is properly given when somebody other than the
>> +original
rrectly when
numeric color values are used.
Changes since v1.5.4 are as follows:
Gerrit Pape (1):
INSTALL: git-merge no longer uses cpio
Jari Aalto (1):
Documentation/git-stash.txt: Adjust SYNOPSIS command syntax (2)
Junio C Hamano (3):
U
it of empty message with commit --amend
Jay Soffian (1):
fast-export: quote paths with spaces
Jeff King (3):
push: don't guess at qualifying remote refs on deletion
add: create ADD_EDIT.patch with mode 0666
commit: fix "--amend --only" with no pathspec
Junio
A release candidate Git v1.7.12-rc0 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
09016e819a69b49090756e9bc5c97a4df25c2f78 git-1.7.12.rc0.tar.gz
e85ad0780ff81eacdb05a10762
Stefan Beller writes:
> +5) "git format-patch HEAD~n"
> +
> +Use "git format-patch HEAD~n" to extract the last n patches from your
> +git repository. They will be be saved in textfiles named
> +
> +0001-Introduce-new-Feature.patch
> +0002-Improve-Documentation.patch
Two comments and a ha
The latest feature release Git v1.7.12 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
42ec1037f1ee5bfeb405710c83b73c0515ad26e6 git-1.7.12.tar.gz
50bbfeba77af9a411cc1a1e41220782cf3fd9b5
Changes since v1.7.11.1 are as follows:
Carlos Martín Nieto (2):
Documentation: --no-walk is no-op if range is specified
git-cherry-pick.txt: clarify the use of revision range notation
Heiko Voigt (1):
update-index: allow overwriting existing
Linus Torvalds writes:
> On Sun, Jan 20, 2013 at 5:32 PM, Rusty Russell wrote:
>>
>> Due to the delay on git.kernel.org, git request-pull fails. It *looks*
>> like it succeeds, except the warning, but (as we learned last time I
>> screwed up), it doesn't put the branchname because it can't know
An early preview Git v1.8.2-rc0 for the upcoming release is now
available for testing at the usual places. The preview includes
contributions from 80+ people, totaling some 570+ no-merge changes
since v1.8.1 and should give you more or less a complete picture of
what the upcoming 1.8.2 would look
empty peg rev
Junio C Hamano (2):
gitcli: parse-options lets you omit tail of long options
Git 1.8.0-rc2
Nguyễn Thái Ngọc Duy (2):
gitignore.txt: suggestions how to get literal # or ! at the beginning
attr: a note about the order of .gitattributes lookup
Ramkumar Rama
format-patch: fix rfc2047 address encoding with respect to rfc822 specials
format-patch tests: check quoting/encoding in To: and Cc: headers
Jeff King (3):
diff_grep: use textconv buffers for add/deleted files
gitweb: escape html in rss title
checkout: print a message when sw
han Nieder (6):
config, gitignore: failure to access with ENOTDIR is ok
config: treat user and xdg config permission problems as errors
doc: advertise GIT_CONFIG_NOSYSTEM
config: exit on error accessing any config file
build: do not automatically reconfigure unless
t;diff --stat" output
was computed incorrectly.
* "diff --shortstat" miscounted the total number of affected files
when there were unmerged paths.
* "update-ref -d --deref SYM" to delete a ref through a symbolic ref
that points to it did not remove it co
ompletion: fix shell expansion of items"
Jens Lehmann (1):
submodule: use argv_array instead of hand-building arrays
Jeremy White (1):
Documentation: describe subject more precisely
Jonathan "Duke" Leto (1):
Improve the description of GIT_PS1_SHOWUPSTREAM
Junio
A release candidate Git v1.8.0-rc0 is now available for testing at
the usual places. There are a couple of leftover features we might
merge before the final release, but other than that, this is meant
to be more or less feature-complete preview of the upcoming 1.8.0.
The release tarballs are foun
Al Viro <[EMAIL PROTECTED]> writes:
> On Sat, Feb 23, 2008 at 02:37:00AM +0100, Jan Engelhardt wrote:
>
>> >do you tend to clone the entire repository repeatedly into a series
>> >of separate working directories
>>
>> Too time consuming on consumer drives with projects the size of Linux.
>
> git
uot;"
Jeff King (4):
push: indicate partialness of error message
Documentation/push: clarify matching refspec behavior
push: document the status output
hash: fix lookup_hash semantics
Junio C Hamano (1):
GIT 1.5.4.3
Kristian H淡gsberg (1):
Rename git-core rpm
Listing the file paths and their sigs included in a tree to make
a snapshot of a tree state sounds fine, and diffing two trees by
looking at the sigs between two such files sounds fine as well.
But I am wondering what your plans are to handle renames---or
does git already represent them?
-
To uns
>>>>> "CL" == Christopher Li <[EMAIL PROTECTED]> writes:
CL> On Sun, Apr 10, 2005 at 12:51:59AM -0700, Junio C Hamano wrote:
>>
>> But I am wondering what your plans are to handle renames---or
>> does git already represent them?
>>
CL&g
> "DL" == David Lang <[EMAIL PROTECTED]> writes:
DL> just wanted to point out that recent news shows that sha1 isn't as
DL> good as it was thought to be (far easier to deliberatly create
DL> collisions then it should be)
I suspect there is no need to do so...
Message-ID: <[EMAIL PROTECTED]
> "PB" == Petr Baudis <[EMAIL PROTECTED]> writes:
PB> I'm wondering if doing
PB> if [ "$(show-diff)" ]; then
PB> git diff | git apply
PB> else
PB> checkout-cache -f -a
PB> fi
PB> would actually buy us some time; or, how common is it for people to have
PB> no local changes whatsoever,
rking tree
clone: correctly report http_fetch errors
git-send-email: avoid duplicate message-ids
Jim Meyering (1):
config.c:store_write_pair(): don't read the byte before a
malloc'd buffer.
Junio C Hamano (3):
git grep shows the same hit repeatedly for unme
Andi Kleen <[EMAIL PROTECTED]> writes:
> I imagined it would check for
>
> +struct file_operations ... = {
> + ...
> + .ioctl = ...
>
> That wouldn't catch the case of someone adding only .ioctl to an
> already existing file_operations which is not visible in the patch context,
> but
Divy Le Ray <[EMAIL PROTECTED]> writes:
> On this topic, I have a question: how do I get to see all the
> netdev-2.6 branches ?
> After cloning a free netdev-2.6 tree, 'git branch' shows only the
> master branch:
> ...
> Cloning
> "git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.
2):
fast-import: Don't use a maybe-clobbered errno value
doc typo: s/prior committing/prior to committing/
Johannes Schindelin (1):
gitk: make Ctrl "+" really increase the font size
Junio C Hamano (8):
builtin-commit.c: remove useless check added by faulty c
Mathieu Segaud <[EMAIL PROTECTED]> writes:
> Signed-off-by: Mathieu Segaud <[EMAIL PROTECTED]>
> ---
> fs/ext4/dir.c |2 +-
> fs/ext4/file.c |2 +-
> fs/ext4/ioctl.c | 161
> ---
> include/linux/ext4_fs.h |3 +-
>
etecting errors.
Jean-Luc Herren (2):
git-add--interactive: Allow Ctrl-D to exit
git-add--interactive: Improve behavior on bogus input
Jeff King (1):
diffcore-rename: cache file deltas
Johan Herland (1):
Mention 'cpio' dependency in INSTALL
Johannes Schindelin
Linus Torvalds <[EMAIL PROTECTED]> writes:
> Actually, the code to finding one '\n' is still needed to avoid the
> (pathological) case of getting a "\No newline", so scrap that one which
> was too aggressive, and use this (simpler) one instead.
>
> Not that it matters in real life, since nobody
Stefan Richter <[EMAIL PROTECTED]> writes:
> Jan Engelhardt wrote:
>>> http://linux.yyz.us/git-howto.html
>>
>> It says
>>
>> """Don't forget to download tags from time to time.
>>
>> git pull only downloads sha1-indexed object data, and the requested
>> remote head. This misses updates to
delin (2):
bundle create: keep symbolic refs' names instead of resolving them
Replace the word 'update-cache' by 'update-index' everywhere
Johannes Sixt (1):
t7003-filter-branch: Fix test of a failing --msg-filter.
Junio C Hamano (11):
format-pat
quot; from fgets.
bundle, fast-import: detect write failure
Johannes Schindelin (2):
Optimize prefixcmp()
shortlog: mention the "-e" option in the usage
Johannes Sixt (2):
git-gui: Move frequently used commands to the top of the context menu.
recv_sideb
Ismail Dönmez <[EMAIL PROTECTED]> writes:
> Saturday 12 January 2008 09:11:23 tarihinde Junio C Hamano şunları yazmıştı:
>> The third rc for the next feature release GIT 1.5.4 is available
>> at the usual places:
>>
>> http://www.kernel.org/pub/software/scm/g
Sam Ravnborg <[EMAIL PROTECTED]> writes:
> I wonder how these tabs came in.
> I am almost sure they were not in my original patch. But as git-send-email
> do not save copies of my sent mails I cannot be sure.
>
> Ingo - do you have a script on your side that could have converted
> the spaces to ta
breakage in combination with --compose
Jakub Narebski (1):
autoconf: define NO_SYS_SELECT_H on systems without .
Johannes Schindelin (1):
pull --rebase: be cleverer with rebased upstream branches
Junio C Hamano (5):
git-submodule: rename shell functions for consistency
git
> "PJ" == Paul Jackson <[EMAIL PROTECTED]> writes:
PJ> There is not a concensus (nor a King Penguin dictate) between the
PJ> "while(1)" and "for(;;)" style to document.
FWIW, linux-0.01 has four uses of "while (1)" and two uses of
"for (;;)" ;-).
./fs/inode.c: while (1) {
./fs/namei.c: w
> "AG" == Andreas Gruenbacher <[EMAIL PROTECTED]> writes:
AG> On Wed, 2005-02-02 at 11:50, Herbert Xu wrote:
>> What if a/b aren't aligned?
AG> If people sort arrays that are unaligned even though the
AG> element size is a multiple of sizeof(long) (or sizeof(u32)
AG> as Matt proposes), they a
npage option sections
instaweb: Minor cleanups and fixes for potential problems
Documentation: Fix man page breakage with DocBook XSL v1.72
Jonathan del Strother (1):
Fixing path quoting in git-rebase
Junio C Hamano (12):
grep with unmerged index
refresh_index_quietly(): express &
Jan Engelhardt <[EMAIL PROTECTED]> writes:
> On Oct 30 2007 12:31, Linus Torvalds wrote:
>>On Tue, 30 Oct 2007, Jeff Garzik wrote:
>>>
>>> Can we change git-am to accept two dashes as well as three? :)
>>
>>Well, git-am actually used to be a lot less strict about the dashes, and
>>we've made it
1 - 100 of 452 matches
Mail list logo
